[
https://issues.apache.org/jira/browse/COUCHDB-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273906#comment-15273906
]
Daniel Münch commented on COUCHDB-2709:
---------------------------------------
Any news on this one? I'm kind of running into a similar issue, however using
nginx as the reverse proxy.
> Replicating through https apache reverse proxy causes timeout error
> -------------------------------------------------------------------
>
> Key: COUCHDB-2709
> URL: https://issues.apache.org/jira/browse/COUCHDB-2709
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 1.6.1
> Reporter: Tim Rutherford
> Attachments: httpd-ssl.conf, httpd.conf
>
>
> Replicating from a remote couchdb database behind a apache reverse proxy over
> an https connection fails.
> Simply changing the connection to use http instead of https allows the
> replication to work. Also, changing the couch configuration to use https
> (port 6984) and replicating from that directly also seems to work. So it
> seems to be a combination of https and a reverse proxy at the same time that
> is causing the issue.
> When analyzing the network traffic with wireshark I can see several requests
> being made from couchdb. The first few requests to the database seem to be
> fine. The request for a specific document looks to be fine in wireshark, but
> is reported as timeout error in couchdbs log. The response looks to be a
> valid http 200 response with the correct data in wireshark.
> Futon shows replication as triggered. The status page shows the replication
> as stuck at 0% and the checkpoint never advances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
