https://issues.apache.org/bugzilla/show_bug.cgi?id=47810
Ivo Timmermans <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #5 from Ivo Timmermans <[email protected]> 2010-04-20 11:23:51 EDT --- (In reply to comment #1) > 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. Sure. But if the backend normally works fine, which it does in my case, the 100-continue will only show up later when the situation occurs. > 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). Agreed on this one. I'll close this bug since the behavior in svn trunk appears to be what I'd expect: the 400 error response from the backend server is properly handled by apache and it will send a 502 Bad gateway to the client. -- 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]
