DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=7513 [EMAIL PROTECTED] changed: What|Removed |Added URL||http://www.xanga.com -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2003-04-10 18:23 --- Strange ... is this bug now invalid or not? (question without deep digging into it) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2003-04-10 22:24 --- I *think* this is invalid. I haven't looked into it since I downgraded to a security-patched version of 1.3.20 on all our web servers that use mod_proxy. If I have time at some point I'd like to try the latest 1.3.* release with HTTP 1.1 mod_proxy and see if I can't figure out why our webapp is causing these problems, and how we can fixed it permanently. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2002-08-16 10:36 --- any word on this? Maybe I am smoking crack on this one?? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2002-07-18 04:36 --- Oops. I meant a security-patched version of 1.3.20 (not 1.3.26) Actually, on futher investigation, I beleive there is something else going on. I am not seeing evidence of a chunked encoding problem when running a proxy through a 1.3.26 server with most pages. However, there is one page, and error handling page, that uses CGI::Carp to override the die() method and pops up our own custom error message in a new window (via Javascript) and logs the error into a database. This page no longer works with the 1.3.26 HTTP/1.1 proxy code, and returns garbled HTML (shown in the attached document 1.3.26_response.txt, as compared with the correctly functioning page returned 1.2.30_reponse.txt) I am going to do some more experiementing to see if I can isolate the problem some more. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2002-07-18 04:37 --- Created an attachment (id=2391) corrupted HTML sent by 1.3.26 mod_proxy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2002-07-18 04:38 --- Created an attachment (id=2392) working HTML from 1.3.20 mod_proxy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients [EMAIL PROTECTED] changed: What|Removed |Added Severity|Blocker |Normal --- Additional Comments From [EMAIL PROTECTED] 2002-07-18 15:26 --- I've been digging much deeper into this, and alas it appears to be a problem with the way the developers programmed the error handling code: They are using it to print HTML and JavaScript that ends up getting printed BEFORE the actual HTTP 500 headers, and this this is corrupting the headers in a way that just happens to work OK when proxied with HTTP/1.0 (under 1.3.20) but not with the HTTP/1.1 proxy code (which seems to be stripping out some of the HTML boilerplate tags that cause the JavaScript functionality to fail on the browser-side. (At least I think that is what is happpening) I need to discuss this with our developers to determine if there is a better (correct) way to handle errors, or look into overriding Apache's error handling of 500 server errors. For those that are interested (maybe nobody :) I have attached two more ASCII dumps of the HTTP/HTML returned to the client browser by both the 1.3.20 proxy and 1.3.26 proxy. I think this bug can be closed, but I'll leave it up to actual Apache developers to determine if this really isn't a problem (which it now seems to me that it isn't.) Sorry for the confusion... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2002-07-18 15:30 --- Created an attachment (id=2397) HTTP/HTML output from 1.3.20 proxy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2002-07-18 15:31 --- Created an attachment (id=2398) HTTP/HTML output from 1.3.26 proxy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients --- Additional Comments From [EMAIL PROTECTED] 2002-07-17 21:13 --- Brian, I think you are confusing the issue a little here. 1.3.20 was an HTTP/1.0 proxy, so of course it used HTTP/1.0 repsonses. 1.3.26 is a 1.1 proxy, so it will properly respond as 1.1 (even to 1.0 clients). The question is, is the proxy using features (like chunked encoding) in its responses to 1.0 clients that are not allowed. (I probably should never have changed the summary way back when this was first submitted; it was originally only about chunked encoding.) So can you tell us exactly what the proxy is doing that is causing problems for your 1.0 clients? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-04-23 13:28 --- *** Bug 8396 has been marked as a duplicate of this bug. ***
DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513 Proxy not downgrading responses for HTTP/1.0 clients [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-04-07 18:58 --- When an HTTP/1.1 server responded to a request with chunked data, this data was passed as is to the frontend server, instead of being dechunked as it was transferred. Through another coincidence, the Transfer-Encoding header made it to the client intact. This resulted in HTTP/1.1 clients handling the data, but HTTP/1.0 clients would barf. The fix was to dechunk chunked data as it arrived.
