httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 53835] New: mod_proxy_ajp truncate output when using deflate input filter
Date Thu, 06 Sep 2012 11:09:44 GMT

          Priority: P2
            Bug ID: 53835
           Summary: mod_proxy_ajp truncate output when using deflate input
          Severity: critical
    Classification: Unclassified
                OS: Linux
          Hardware: PC
            Status: NEW
           Version: 2.2.15
         Component: mod_proxy_ajp
           Product: Apache httpd-2


I need to activate a setInputFilter DEFLATE in our vhost to provide gzip
compression from our clients (iphone app) to our java app.

If I activate the DEFLATE filter, AJP proxy truncates to only one 8K packet and
send it as is  to the backend.
Without any deflate input filter, the big body (more than 8K) is correctly sent
to the Java backend.

If I understand well, AJP is a packet oriented protocol (max 8k chunk by
When apache receives the request, it decompresses the body as expected but it
seems to send the whole thing to the proxy and this one send only 8k to the
backend. The rest of the packet seems to be lost.

To make a small test, I tried sending a small packet (less than 8k ungzipped) :
it works
I also tried to modify the following parameter in tomcat AJP connector :
'packetSize' and 'ProxyIOBufferSize' in apache to match a bigger value than 8k
(65535). In this case, if I send my 11k packet, it works like a charm.

Finally, if we use http instead of ajp in the proxy configuration, everything
works great. The problem definitly comes from AJP protocol itself.

So my conclusion is that there is a bug with mod_proxy_ajp when using input
filter. What do you think ?

Nicolas Maupu

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message