Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Add a comment about server-injected Content-Length header.
  • Loading branch information
mcdonc committed Sep 2, 2010
1 parent 9838e03 commit 8a27481
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions web3.rst
Expand Up @@ -108,10 +108,14 @@ Differences from WSGI

- ``SERVER_PORT`` must be a bytes instance (not an integer).

- The server must not inject an additional content-length header by
guessing the length from the response iterable. This must be set
- The server must not inject an additional ``Content-Length`` header
by guessing the length from the response iterable. This must be set
by the application itself in all situations.

.. XXX (chrism) I'm -0 on this; this behavior doesn't seem that
harmful. If we do keep it, we need to remove the bit in
"Specification Details" about ``len(body)``.
- If the origin server advertises that it has the ``web3.async``
capability, a Web3 application callable used by the server is
permitted to return a callable that accepts no arguments. When it
Expand Down

0 comments on commit 8a27481

Please sign in to comment.