Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.2.4
-
None
-
Unknown
Description
One of our clients always sends 'Expect: 100-continue' headers and expects the server to respond with status code 100 Continue before sending the payload of the request. With transport untertow, this is currently not supported (we see an additional delay of 2s per request)
The issue can be resolved by wiring in the io.undertow.server.handlers.HttpContinueReadHandler.
For example modifying these lines works:
if (url.getPath().length() == 0) { result = result.setHandler(Handlers.trace(new HttpContinueReadHandler(undertowHTTPHandler))); } else { if (undertowHTTPHandler.isContextMatchExact()) { this.path.addExactPath(url.getPath(), new HttpContinueReadHandler(undertowHTTPHandler)); } else { this.path.addPrefixPath(url.getPath(), new HttpContinueReadHandler(undertowHTTPHandler)); } result = result.setHandler(this.wrapHandler(this.path)); }
Alternative impl to integrate this handler in UndertowHTTPHandler.
Also the config should really be set via cxf.xml.
Test case:
- Deploy a simple SOAP service using javax.xml.ws.Endpoint.publish
- Configure SoapUI in preferences > HTTP Settings (Expect-Continue: true)
- Call a SOAP operation
100-Continue is well supported in the jetty transport, but with netty we see a similar issue. With netty the server hangs and doesn't respond