[Python-checkins] python/nondist/peps pep-0333.txt,1.8,1.9
pje at users.sourceforge.net
pje at users.sourceforge.net
Tue Sep 14 07:06:46 CEST 2004
Update of /cvsroot/python/python/nondist/peps
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8842
Modified Files:
pep-0333.txt
Log Message:
Forgot to include the language about suppressing the logging of header
overrides, that was discussed in:
http://mail.python.org/pipermail/web-sig/2004-September/000749.html
Also, misc. copy edits.
Index: pep-0333.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0333.txt,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- pep-0333.txt 13 Sep 2004 20:01:54 -0000 1.8
+++ pep-0333.txt 14 Sep 2004 05:06:44 -0000 1.9
@@ -560,6 +560,9 @@
However, if a server or gateway discards or overrides any application
header for any reason, it **must** record this action in a log (such as
the ``wsgi.errors`` log) for the benefit of the application author.
+(However, it **may** also give administrators the option of suppressing
+such output, so that users who cannot fix a broken application are not
+forced to bear the pain of its error.)
The ``start_response`` callable **must not** actually transmit the
HTTP headers. It must store them until the first ``write`` call,
@@ -1143,7 +1146,7 @@
may be done in any of several ways:
1. Reject all client requests containing an ``Expect: 100-continue``
- header with a "417 Expectation failed" error. Such requests will
+ header with a "417 Expectation failed" error. Such requests should
not be forwarded to an application object.
2. Respond to requests containing an ``Expect: 100-continue`` request
@@ -1155,7 +1158,7 @@
input stream. The read request must then remain blocked until the
client responds.
-Note that this behavior restriction does not apply for HTTP 1.0
+Note that these behavior restrictions do not apply for HTTP 1.0
requests, or for requests that are not directed to an application
object. For more information on HTTP 1.1 Expect/Continue, see RFC
2616, sections 8.2.3 and 10.1.1.
More information about the Python-checkins
mailing list