GitHub user nickva opened a pull request:

    https://github.com/apache/couchdb-chttpd/pull/143

    Add max_document_size checking for multipart PUT requests

    Previously multipart/related PUT requests didn't check maximum request 
sizes.
    
    This commit checks content-length and compares that with the maximum.
    
    This means keeping the current "semantics" of max_document_size which 
actually
    means "max request size". But this makes the check more efficient and can
    be done earlier in request processing time.
    
    PR depends on https://github.com/apache/couchdb-couch/pull/201 make sure to
    merge that one first if accepted.
    
    Jira: COUCHDB-3174

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloudant/couchdb-chttpd couchdb-3174

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-chttpd/pull/143.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #143
    
----
commit 5d7170c472d2ca72d4a0dd41eb7ae4434266be7d
Author: Nick Vatamaniuc <[email protected]>
Date:   2016-10-04T06:58:32Z

    Add max_document_size checking for multipart PUT requests
    
    Previously multipart/related PUT requests didn't check maximum request 
sizes.
    
    This commit checks content-length and compares that with the maximum.
    
    This means keeping the current "semantics" of max_document_size which 
actually
    means "max request size". But this makes the check more efficient and can
    be done earlier in request processing time.
    
    PR depends on https://github.com/apache/couchdb-couch/pull/201 make sure to
    merge that one first if accepted.
    
    Jira: COUCHDB-3174

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to