Bug 53835 - mod_proxy_ajp truncate output when using deflate input filter
Summary: mod_proxy_ajp truncate output when using deflate input filter
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_ajp (show other bugs)
Version: 2.2.15
Hardware: PC Linux
: P2 critical (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2012-09-06 11:09 UTC by nmaupu@gmail.com
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nmaupu@gmail.com 2012-09-06 11:09:44 UTC
Hello,

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 default).
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 ?

Regards,
Nicolas Maupu
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:20 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.