couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1777) 409 response vs persitent connection
Date Fri, 26 Apr 2013 02:03:13 GMT


Adam Kocoloski commented on COUCHDB-1777:

Interesting.  I can't think of any good reason why CouchDB would force the connection to close.
 CouchDB relies directly on mochiweb for connection management and its rules for determining
whether to keep the connection are fairly straightforward.

Marek, is this a PUT request with a plain JSON body or something more exotic like a multipart
> 409 response vs persitent connection
> ------------------------------------
>                 Key: COUCHDB-1777
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>            Reporter: Marek Kowalski
> CouchDB closes the persistent client connection after responding with 409 code. This
behavior is not necessarily against the RFC 2616, although it makes it more complicated to
use pipelining. 
> If its really necessary to close the connection, it would be nice to at least put the
"Connection: close" in the response headers. If the connection can be closed without informing
client that this is going to happen, the client might start writing the new request to the
connection. Again, according RFC 2616, this situation should be handled by the client, although
the header could be added "as a courtesy".

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message