[
https://issues.apache.org/jira/browse/COUCHDB-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876368#comment-15876368
]
ASF subversion and git services commented on COUCHDB-3293:
----------------------------------------------------------
Commit 2a263f84db62e4849a41322b92588c6893169198 in couchdb-couch's branch
refs/heads/COUCHDB-3287-mixed-db-records from [~vatamane]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-couch.git;h=2a263f8 ]
Allow limiting length of document ID
Previously it was not possibly to define a maxum document ID size. That meant
large document ID would hit various limitations and corner cases. For example,
large document IDs could be inserted via a _bulk_docs endpoint but then trying
to insert the same document via a single HTTP method like PUT would fail
because of a limitation in Mochiweb's HTTP parser.
Let operators specify a maxium document ID length via the
```
couchdb.max_document_id_length = infinity | Integer
```
configuration.
The default value of `infinity` keeps the current behavior where document
ID length is not checked.
COUCHDB-3293
> Configure maximum document ID length
> ------------------------------------
>
> Key: COUCHDB-3293
> URL: https://issues.apache.org/jira/browse/COUCHDB-3293
> Project: CouchDB
> Issue Type: New Feature
> Reporter: Nick Vatamaniuc
>
> Allow users / operators to specify maximum document ID length.
> Currently it is easy to break CouchDB by feeding it large IDs through
> _bulk_docs endpoint but which will hit the limits of http parser if sent
> through GET/PUT/DELETE methods. In case those limits are hit the error
> returned is not obvious as the requests would often crash in the mochiweb
> http parser step before a request even makes to CouchDB code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
