Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Subject: [Bug 53727] New: mod_proxy_ajp + mod_deflate = mixed up response,
 after accessed by browser that doesn't support gzip
Date: Thu, 16 Aug 2012 05:41:34 +0000
Message-ID: <bug-53727-7868@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=53727

          Priority: P2
            Bug ID: 53727
          Assignee: bugs@httpd.apache.org
           Summary: mod_proxy_ajp + mod_deflate = mixed up response, after
                    accessed by browser that doesn't support gzip
          Severity: critical
    Classification: Unclassified
                OS: Linux
          Reporter: sokann@gmail.com
          Hardware: PC
            Status: NEW
           Version: 2.4.2
         Component: mod_proxy_ajp
           Product: Apache httpd-2

1. Create a simple web app and serve it with ajp
2. In the web app, create a normal page (with .js, .css, and images), then
craft a slow page that only returns a response after 1 second
3. Setup a reversed proxy to the web app with mod_proxy_ajp (a plain ProxyPass
line)
4. Enable mod_deflate for the usual content types
5. Open Firefox, go to about:config, and set network.http.accept-encoding from
"gzip, deflate" to an empty string
6. Restart Firefox, clear cache
7. With Firefox, access the normal page and let it load to completion, then
access the slow page and press "Ctrl-W" to close the tab before the response is
returned
8. Open Chrome, clear cache
9. With Chrome, access the normal page and see things go haywire, e.g. a
request for a .js file will receive a response of image/png

The symptom of mixed up response is similar to bug 40310 and bug 47714. In
production system, other than broken functionality caused by .js file returned
as image, our users were able to see responses intended for others.

Once things go haywire, a graceful reload of Apache will get things to work
again (leaving browser and proxy caching aside), until the next non-gzip client
abandons a page load.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org