You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Isaac Z. Schlueter (JIRA)" <ji...@apache.org> on 2014/02/13 08:34:20 UTC

[jira] [Created] (COUCHDB-2059) CouchDB replicator sends urls that are too long for comfort

Isaac Z. Schlueter created COUCHDB-2059:
-------------------------------------------

             Summary: CouchDB replicator sends urls that are too long for comfort
                 Key: COUCHDB-2059
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2059
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Replication
            Reporter: Isaac Z. Schlueter


I have my couchdb behind an TLS terminator.  Like most HTTP servers, it has a limit on how long URLs can be, and that limit is far smaller than the 6-12KB urls that the CouchDB replicator is sending.

https://gist.github.com/isaacs/0010221834a3491d6481
http://cl.ly/image/3N192G293j1R

This is a bug, right?

For added frustration:

1. The replication never goes into a failed state.  Just stays "triggered" forever, doing nothing, hung at 77%.
2. The logs are indented with over 6000 spaces.  I've been known to do some crazy code formatting in my time, but this is too extreme, and makes reading the log unnecessarily difficult.

Suggestion:

Limit the length of URLs that the replicator will use to something more reasonable, such as 1024 bytes.  If more data than that is required, send it in the body of the request.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)