Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Thu, 13 Feb 2014 10:14:19 +0000 (UTC)
From: "Robert Newson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12694935.1392276770111.36104.1392286459512@arcas>
In-Reply-To: <JIRA.12694935.1392276770111@arcas>
References: <JIRA.12694935.1392276770111@arcas>
Subject: [jira] [Commented] (COUCHDB-2059) CouchDB replicator sends urls
 that are too long for comfort
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900187#comment-13900187 ] 

Robert Newson commented on COUCHDB-2059:
----------------------------------------

hah, well;

-define(MAX_URL_LEN, 7000).

We can make that a config thing.


> 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)