couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] Closed: (COUCHDB-433) CouchDB doesn't handle Expect header.
Date Sat, 21 Nov 2009 17:18:39 GMT


Adam Kocoloski closed COUCHDB-433.

       Resolution: Fixed
    Fix Version/s: 0.11
         Assignee: Adam Kocoloski

Issue 42 was fixed upstream in r103; we're now at r113.  The custom test passes, so closing
this one out.

> CouchDB doesn't handle Expect header.
> -------------------------------------
>                 Key: COUCHDB-433
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 0.10
>            Reporter: Robert Newson
>            Assignee: Adam Kocoloski
>             Fix For: 0.11
>         Attachments: 0001-fix-e-c-handling.patch
> An HTTP client may elect to send an "Expect: 100-Continue" header. All compliant HTTP
servers are required to;
> "A server that does not understand or is unable to comply with any of the expectation
values in the Expect field of a request MUST respond with appropriate error status. The server
MUST respond with a 417 (Expectation Failed) status if any of the expectations cannot be met
or, if there are other problems with the request, some other 4xx status."
> from
> CouchDB sends neither the Continue response (if it supports expect-continue) or 417 (if
it doesn't).
> This leads clients that include the header to hang while they timeout expecting either
> Suggest returning a 417 response so that compliant clients will retry immediately without
the Expect header.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message