Bug 57069 - apache ssl timeout during chunked request in reverse balanced proxy setup
Summary: apache ssl timeout during chunked request in reverse balanced proxy setup
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_ssl (show other bugs)
Version: 2.2.29
Hardware: PC Mac OS X 10.4
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2014-10-08 16:15 UTC by Valentin Kuznetsov
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Kuznetsov 2014-10-08 16:15:47 UTC
Hi, we're trying to solve very mysterious problem with apache frontend serving as reverse proxy for our CouchDB back-end servers. In production we have apache 2.2.25 version with the following configuration settings [1]. It correctly redirects traffic to our CouchDB backend (version 1.1). When we try new version of CouchDB (version 1.5, 1.6) we see timeouts in back-end log and our replication process does not proceed. The difference in CouchDB replication between different version is that latest ones rely on "Transfer-Encoding: chunked" while former does not. We enabled dumpio module in apache to get a snapshot of the traffic and what we see is replication process in progress, but it is aborted due to SSL timeout. Here [2] you can see server part of this process (I stripped off sensitive parts). I tried various apache proxy settings (proxy-sendchunks, etc) but nothing helps, except if I'll turn on downgrade-1.0. Using this option the replication works. Moreover, we did tested apache 2.4 and it works too without any tweaking. I also tested that problem exists with latest apache 2.2.29 version. I would appreciate any help/suggestions on how to debug this issue.

[1] https://gist.github.com/vkuznet/cd8338f8a309ae788142
[2] https://gist.github.com/vkuznet/8bb84a31eb5e40b0e255
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:53 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.