couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2059) CouchDB replicator sends urls that are too long for comfort
Date Mon, 17 Feb 2014 14:18:20 GMT


Robert Newson commented on COUCHDB-2059:
---------------------------------------- is updated, minimum is 200, and I added a server
config setting that causes CouchDB itself to send 414 for uri's over the configured length
(default is infinite). This is handy for testing the negotiation but server admins might find
it helpful to align couchdb's max uri length with any intermediate proxy with a uri length

> CouchDB replicator sends urls that are too long for comfort
> -----------------------------------------------------------
>                 Key: COUCHDB-2059
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Replication
>            Reporter: Isaac Z. Schlueter
>             Fix For: 1.7.0
> 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.
> 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

View raw message