https://issues.apache.org/bugzilla/show_bug.cgi?id=47810
Nick Kew <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Nick Kew <[email protected]> 2010-02-20 00:43:23 UTC --- I think you're wrong here. Please reopen if you can convince me otherwise! The 100-Continue is sent *after* the backend has been contacted. A quick and simple demonstration of this is to give it a nonexistent backend: then it returns 503 with no intermediate 100. The argument that the proxy should listen for a response before sending 100-continue is a fine one, and is problematic because it introduces a high latency into regular requests (a round trip to the backend before replying 100). Bear in mind that clients will typically have very short timeouts on waiting for 100-continue before they continue anyway (as they should do, in the absence of an error response). You write: > Then, unexpectedly, apache will continue sending the body, even though the > server hasn't done anything yet. Now, if the server doesn't respond with "100 > Continue", but, for example, with "401 Unauthorized", then the body will be > interpreted as the next request. This is a bug in your backend. We've very recently tackled it in Apache HTTPD: see Bug 47087 (which also details the relevant points of the protocol). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
