You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Joan Touzet (JIRA)" <ji...@apache.org> on 2017/05/16 18:04:04 UTC

[jira] [Closed] (COUCHDB-3420) We have a GET query to fetch data from couchDB, ba...

     [ https://issues.apache.org/jira/browse/COUCHDB-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joan Touzet closed COUCHDB-3420.
--------------------------------
    Resolution: Won't Fix

> We have a GET query to fetch data from couchDB, ba...
> -----------------------------------------------------
>
>                 Key: COUCHDB-3420
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3420
>             Project: CouchDB
>          Issue Type: Bug
>            Reporter: ASF subversion and git services
>
> We have a GET query to fetch data from couchDB, based on criteria, sometimes it gets longer that 4200 chars (query string, including hostname).
> When the query gets longer than 4200 chars, we are not able to fetch data (even using curl), we get HTTP 413 (Request entity too large)
> Strange this is, if we hit the query using Chrome, then anyting longer that 4080 chars, we get HTTP 413 issue. Also, we have NodeJS server to fetch data, and we use cradle to connect to couchDB, in this configuration anything longer that 3400 chars, throws 413 issue.
> My question is
> 1. What is the exact limit and how to find it?
> 2. Why different clients have different limit
> PS: in all the cases the error is reported in couch log file, so it is couch which is throwing this issue and not client.
> *Reporter*: Chetan
> *E-mail*: [mailto:ctinguria@themix.org]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)