Forum Discussion

dkwakkel's avatar
7 years ago

SoapUI not working with Expect 100-continue header

Following scenario:

  1. Install on a windows machine tomee plus 1.7.3:
  2. Copy attached echo.war to <tomee install directory>/webapps and wait till deploy of webapp is finished
  3. Create a soap ui project with following wsdl (you must provide your NTLM credentials): http://<hostname>/echo/webservices/EchoWebservice?wsdl
  4. Test the soap method: it is working (see attached working_without_expect_header.xml)
  5. Enable 'Expect-continue' header in soap ui preferences => http settings
  6. Test the soap method: it is no longer working (see attached not_working_with_expect_header.xml)

For non working following is happening: 

  1. soap ui sends soap request with expect header and without authentication
  2. tomee / tomcat responds with 401 because authentication is not present and closes the connection (see also
    A server that responds with a final status code before reading the
    entire message body SHOULD indicate in that response whether it
    intends to close the connection or continue reading and discarding
    the request message (see Section 6.6 of [RFC7230]).
  3. Next soap ui sends again the request with an NTLM authentication negotiate with expect header. Tomee respond with 401, ntlm challenge and again closes the connection.
  4. Next soap ui sends again the request with NTLM authentication with expect header. Tomee respond with 401 because it can not connect the challenge to this authentication information (NTLM is a connection based authentication protocol).

In my opinion:

  1. Soap UI must not send the expect header when sending the NTLM negotiate.
  2. Soap UI could choose to not send the POST body when sending the NTLM negotiate.
  3. Soap UI could wait some time (e.g. as .Net 350 ms) before sending payload. Else 100-continue has no use.

Am I correct 1 is a bug? And what about the other two?


Also when I let the tomee server with a valve return 417 expectation failed header soap ui can not handle it (it should repost without Expect header)

No RepliesBe the first to reply