https://bz.apache.org/bugzilla/show_bug.cgi?id=63855
Yann Ylavic <ylavic....@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #36848|0 |1
is obsolete| |
--- Comment #15 from Yann Ylavic <ylavic....@gmail.com> ---
Created attachment 36849
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36849&action=edit
Send 100-continue (if needed) when spooling the request body (v3)
Indeed, v2 does not work because it's too late (in mod_proxy_http's spooling
function) to rely on the HTTP input filter to send the "100 Continue". Sorry
for the useless testing.
Back to the same fix as with the first patch with this v3, plus the handling of
the "100 Continue" status line directly in ap_send_interim_response() (which
adds quite some "noise" because it requires to merge ap_get_status_line_ex()
which was trunk only so far).
Could you please test it so that I can propose it for 2.4.x?
As for "Proxy100Continue off", it forces mod_proxy to handle the 100-continue
expectation immediately, and thus fetch/forward the body on its own regardless
of the backend (origin) intent. This may be what you want (since mod_security
prevents 100-continue forwarding anyway), but it kind of defeats the purpose of
100-continue IMHO.
Another option is to "SetEnv proxy-sendchunks" as you noticed, but it requires
that the backends supports chunk encoding in requests (shouldn't be an issue
these days).
Last option (I can think of) would be to convince the mod_security team to
register their input filter as a protocol filter (as opposed to a content
filter), such that mod_proxy can forward the original Content-Length...
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
