You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by fl...@apache.org on 2017/10/23 09:34:53 UTC
[couchdb-documentation] branch status413 updated (d52032e ->
d81c7a0)
This is an automated email from the ASF dual-hosted git repository.
flimzy pushed a change to branch status413
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git.
omit d52032e Document that a 413 status may be returned.
new 062dd37 Document that a 413 status may be returned.
new d81c7a0 Fix a couple typos, and add links
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d52032e)
\
N -- N -- N refs/heads/status413 (d81c7a0)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
src/api/basics.rst | 4 +++-
src/config/couchdb.rst | 6 +++---
src/config/http.rst | 11 ++++++-----
3 files changed, 12 insertions(+), 9 deletions(-)
--
To stop receiving notification emails like this one, please contact
['"commits@couchdb.apache.org" <co...@couchdb.apache.org>'].
[couchdb-documentation] 02/02: Fix a couple typos, and add links
Posted by fl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
flimzy pushed a commit to branch status413
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git
commit d81c7a07acd4a787b5128e030663c26efe55b666
Author: Jonathan Hall <fl...@flimzy.com>
AuthorDate: Mon Oct 23 11:23:36 2017 +0200
Fix a couple typos, and add links
---
src/config/couchdb.rst | 6 +++---
src/config/http.rst | 11 ++++++-----
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/src/config/couchdb.rst b/src/config/couchdb.rst
index c44b3cd..9c2fb0b 100644
--- a/src/config/couchdb.rst
+++ b/src/config/couchdb.rst
@@ -213,6 +213,6 @@ Base CouchDB Options
http request body sizes. For individual document updates via `PUT`
that approximation was close enough, however that is not the case
for `_bulk_docs` endpoint. After 2.1.0 a separate configuration
- parameter was defined: httpd.max_http_request_size, which can be
- used to limit maximum http request sizes. After upgrade, it is
- advisable to review those settings and adjust them accordingly.
+ parameter was defined: :config:option:`httpd/max_http_request_size`,
+ which can be used to limit maximum http request sizes. After upgrade,
+ it is advisable to review those settings and adjust them accordingly.
diff --git a/src/config/http.rst b/src/config/http.rst
index f38a31f..1330da2 100644
--- a/src/config/http.rst
+++ b/src/config/http.rst
@@ -214,17 +214,18 @@ HTTP Server Options
`PUT` of a document larger than 1MB, but it might also block a
`_bulk_docs` update of 1000 1KB documents, or a multipart/related
update of a small document followed by two 512KB attachments. This
- setting is intended to be used as a protection aginst maliciously
+ setting is intended to be used as a protection against maliciously
large HTTP requests rather than for limiting maximum document sizes. ::
[httpd]
max_http_request_size = 4294967296 ; 4 GB
.. warning::
- Before version 2.1.0 couchdb.max_document_size was implemented
- effectively as max_http_request_size. That is, it checkeded HTTP
- request bodies instead of document sizes. After the upgrade, it is
- advisable to review the usage of these configuration settings.
+ Before version 2.1.0 :config:option:`couchdb/max_document_size` was
+ implemented effectively as ``max_http_request_size``. That is, it
+ checked HTTP request bodies instead of document sizes. After the
+ upgrade, it is advisable to review the usage of these configuration
+ settings.
.. config:section:: chttpd :: Clustered HTTP Server Options
--
To stop receiving notification emails like this one, please contact
"commits@couchdb.apache.org" <co...@couchdb.apache.org>.
[couchdb-documentation] 01/02: Document that a 413 status may be
returned.
Posted by fl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
flimzy pushed a commit to branch status413
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git
commit 062dd37be235d244b73837bba6a27bc14b7afcc1
Author: Jonathan Hall <fl...@flimzy.com>
AuthorDate: Mon Oct 23 10:50:57 2017 +0200
Document that a 413 status may be returned.
---
src/api/basics.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/api/basics.rst b/src/api/basics.rst
index 87fd083..b1d84f4 100644
--- a/src/api/basics.rst
+++ b/src/api/basics.rst
@@ -568,6 +568,12 @@ specific request types are provided in the corresponding API call reference.
The request headers from the client and the capabilities of the server do not
match.
+- ``413 - Request Entity Too Large``
+
+ A document exceeds the configured :config:option:`couchdb/max_document_size`
+ value or the entire request exceeds the
+ :config:option:`httpd/max_http_request_size` value.
+
- ``415 - Bad Content Type``
The content types supported, and the content type of the information being
--
To stop receiving notification emails like this one, please contact
"commits@couchdb.apache.org" <co...@couchdb.apache.org>.