Skip to content

Require server to handle Content-Length headers when receiveing HTTP requests #510

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions specs/www.rst
Original file line number Diff line number Diff line change
@@ -23,6 +23,7 @@ This spec has had the following versions:
* ``2.3``: Added the ``reason`` key to the WebSocket close event.
* ``2.4``: Calling ``send()`` on a closed connection should raise an error
* ``2.5``: Added the ``reason`` key to the WebSocket disconnect event.
* ``2.6``: Added mandatory consistency checks for ``Content-Length`` on HTTP requests.

Spec versions let you understand what the server you are using understands. If
a server tells you it only supports version ``2.0`` of this spec, then
@@ -176,6 +177,13 @@ Keys:
processed. Optional; if missing defaults to ``False``.


The server *must not* read past the client’s specified ``Content-Length``, and
*should* simulate an end-of-file condition if the application attempts to read past that
point. The server *may* respond with an 'HTTP 400 - Bad Request' error code in case the
request body exceeds the announced content length.
(This behaviour was introduced in spec version 2.6)


Response Start - ``send`` event
'''''''''''''''''''''''''''''''