-
Enhancement
-
Resolution: Done
-
Major
-
7.1.0.GA
-
None
Previously, EAP 6/JBossWeb always sent the 100-continue response. And mod_proxy_http happens to always expect a 100-continue response for proxied POST requests, even if it sent request data. So this combination worked fine.
But now, Undertow chooses to omit the 100-continue if it received data. This is allowed per the spec, but it causes unwanted behavior in mod_proxy_http. Without the 100-continue being sent, slower POSTs can reach the proxy ping timeout and induce unwanted error states.
Would an option be possible to make Undertow behave like JBossWeb so it always send the 100-continue even if request data has been received so that issues like this with mod_proxy_http or other proxies/clients strictly expecting the 100-continue can be avoided?
- incorporates
-
UNDERTOW-1281 Option to have 100-continue response sent even if request body has come
- Resolved
- is caused by
-
JBCS-451 mod_proxy_http incorrectly requires continue response after already sending response data
- Closed
- is cloned by
-
JBEAP-14288 [GSS](7.0.z) Option to have 100-continue response sent even if request body has come
- Closed
- is incorporated by
-
JBEAP-14208 (7.1.z) Upgrade Undertow from 1.4.18.SP2-redhat-1 to 1.4.18.SP5-redhat-1
- Closed
-
JBEAP-14288 [GSS](7.0.z) Option to have 100-continue response sent even if request body has come
- Closed