DO NOT REPLY [Bug 13101] New: - Using mod_ext_filter with mod_proxy and http/1.1 causes bogus output

From: <bugzilla(at)apache.org>
Date: Fri Sep 27 2002 - 17:50:14 EDT

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=13101>. 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=13101

Using mod_ext_filter with mod_proxy and http/1.1 causes bogus output

           Summary: Using mod_ext_filter with mod_proxy and http/1.1 causes
                    bogus output
           Product: Apache httpd-2.0
           Version: 2.0.42
          Platform: PC
               URL: 
http://spiff.melthusia.org/~gtetlow/filter-bug.txt
        OS/Version: FreeBSD
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: mod_ext_filter
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: gordont@gnf.org

I have a content rewriting proxy that uses mod_ext_filter to rewrite content.
Everything was working beautifully on Apache 2.0.40. I upgraded to 2.0.42 and using junk started to show up in my filter. I would get numbers showing up at the beginning and the end of the response. If I use a BrowserMatch to downgrade-1.0 for all cases, it seems to work. This leads me to believe that the bug is not in mod_ext_filter, but some interaction with the core.

This is very reproducable for me. I can even use a filter of /bin/cat and get this problem so I'm *certain* this is not my filter.

I'm out of town from 9/27 - 10/6 so I may to be able to respond to this bug immediately.

The URL shows a trace of 3 sessions, one 2.0.40 with HTTP/1.1, one 2.0.42 with HTTP/1.1 (bugged), and one 2.0.42 with HTTP/1.0.

---

To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org Received on Fri Sep 27 21:49:28 2002