https://bz.apache.org/bugzilla/show_bug.cgi?id=63626
--- Comment #6 from Yann Ylavic <ylavic....@gmail.com> --- AIUI, the purpose of the 100-continue mechanism is to ping the service, as opposed to ping the (TCP-)connection. In this case the client sent the HTTP header with "Expect: 100-continue", mod_proxy_http forwarded it (TCP connect/reuse works) but did *not* respond with the interim "100 continue" message yet (since httpd-2.4.41 and bug 60330 ;) ). So no body has been engaged yet and the service can be considered unavailable, i.e. the client or mod_proxy can send the non-idempotent request elsewhere since the previous attempt was consciously incomplete. -- 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
