Skip to content
Permalink
Browse files
Merge pull request #723 from big-r81/fix-status-codes
Fix status codes rendering
  • Loading branch information
big-r81 committed May 5, 2022
2 parents 39c22ba + 801b94a commit 146d1a990b0ab594f179ab1408ec19396f43ab40
Showing 5 changed files with 17 additions and 16 deletions.
@@ -1,2 +1,3 @@
Sphinx==2.4.4
sphinx-rtd-theme==1.0.0
jinja2<3.1
@@ -385,8 +385,8 @@ Two sections of config exist to configure JWT authentication;

The :config:option:`required_claims <jwt_auth/required_claims>` config
setting is a comma-separated list of additional mandatory JWT claims
that must be present in any presented JWT token. A `:code 400:Bad
Request` is sent if any are missing.
that must be present in any presented JWT token. A :statuscode:`400`
is sent if any are missing.

The ``alg`` claim is mandatory as it used to lookup the correct key for verifying the
signature.
@@ -407,8 +407,8 @@ list as long as the JWT token is valid.
; Examples
; hmac:_default = aGVsbG8=
; hmac:foo = aGVsbG8=
; The config values can represent symmetric and asymmetrics keys.
; For symmetrics keys, the value is base64 encoded;
; The config values can represent symmetric and asymmetric keys.
; For symmetric keys, the value is base64 encoded;
; hmac:_default = aGVsbG8= # base64-encoded form of "hello"
; For asymmetric keys, the value is the PEM encoding of the public
; key with newlines replaced with the escape sequence \n.
@@ -361,8 +361,8 @@ Authentication Configuration
.. config:option:: required_claims :: Mandatory claims in JWT tokens
This parameter is a comma-separated list of additional mandatory JWT claims
that must be present in any presented JWT token. A
`:code 400:Bad Request` is sent if any are missing. ::
that must be present in any presented JWT token. A :http:statuscode:`404`
is sent if any are missing. ::

[jwt_auth]
required_claims = exp,iat
@@ -112,7 +112,7 @@ When working on a single node, CouchDB will avoid creating conflicting revisions
by returning a :statuscode:`409` error. This is because, when you
PUT a new version of a document, you must give the ``_rev`` of the previous
version. If that ``_rev`` has already been superseded, the update is rejected
with a :statuscode:`409` response.
with a :statuscode:`409` response.

So imagine two users on the same node are fetching Bob's business card, updating
it concurrently, and writing it back:
@@ -176,7 +176,7 @@ Bugfixes
This should resolve a long-standing gradual memory increase bug in CouchDB.

* :ghissue:`2613`: Simultaneous attempts to create the same new database should
no longer result in a :code 500: error.
no longer result in a :statuscode:`500` error.

* :ghissue:`2678`: Defaults for the ``smoosh`` compaction daemon are now consistent
with the shipped ``default.ini`` file.
@@ -268,9 +268,9 @@ Features and Enhancements

* :ghissue:`1875`, :ghissue:`2437`, :ghissue:`2423`: CouchDB now supports linking against
SpiderMonkey 60 or SpiderMonkey 1.8.5. SpiderMonkey 60 provides enhanced support for
ES5, ES6, and ES2016+. Full compatibility information is available at the `ECMAScript
compatibility table`_: click on "Show obsolete platforms," then look for "FF 60 ESR"
in the list of engine types.
ES5, ES6, and ES2016+. Full compatibility information is available at the
`ECMAScript compatibility table`_. Click on "Show obsolete platforms", then look for
"FF 60 ESR" in the list of engine types.

However, it was discovered that on some ARM 64-bit distributions, SM 60 segfaults
frequently, including the SM 60 packages on CentOS 8 and Debian 10.
@@ -419,7 +419,7 @@ Bugfixes
to match other case clauses.

* :ghissue:`1897`: The ``/{db}/_bulk_docs`` endpoint now correctly catches invalid
(*i.e.*, non-hexadecimal) ``_rev_`` values and responds with a :code 400: error.
(*i.e.*, non-hexadecimal) ``_rev_`` values and responds with a :statuscode:`400` error.

* :ghissue:`2321`: CouchDB no longer requires Basic auth credentials to reach the
``/_session`` endpoint for login, even when ``require_valid_user`` is enabled.
@@ -435,8 +435,8 @@ Bugfixes
* :ghissue:`2153`: CouchDB no longer may return a ``badmatch`` error when querying
``all_docs`` with a passed ``keys`` array.

* :ghissue:`2137`: If search is not available, return a :code 400: instead of a
:code 500: status code.
* :ghissue:`2137`: If search is not available, return a :statuscode:`400` instead of a
:statuscode:`500` status code.

* :ghissue:`2077`: Any failed ``fsync(2)`` calls are now correctly raised to avoid
data corruption arising from retry attempts.
@@ -540,8 +540,8 @@ The 3.0.0 release also includes the following minor improvements:
* :ghissue:`2337`: The md5 shim (introduced to support FIPS-compliance) is now
used consistently throughout the code base.

* :ghissue:`2270`: Negative and non-integer ``heartbeat`` values now return :code 400:
Bad Request.
* :ghissue:`2270`: Negative and non-integer ``heartbeat`` values now return
:statuscode:`400`.

* :ghissue:`2268`: When rescheduling jobs, CouchDB now stops sufficient running jobs
to make room for the pending jobs.

0 comments on commit 146d1a9

Please sign in to comment.