Graham Dumpleton ha scritto:
Just noticed that although WSGI PEP doesn't specifically mention that argument to read() on wsgi.input is optional, wsgiref.validate allows calling read() with no argument.
wsgiref.validate makes also other assumptions about a WSGI application that are not required by the WSGI PEP. As an example it reports as an error the presence in the environ dictionary of HTTP_CONTENT_TYPE and HTTP_CONTENT_LENGTH, but the PEP says nothing about this, and CGI [1] says: """"The server may exclude any headers which it has already processed, such as Authorization, Content-type, and Content-length. If necessary, the server may choose to exclude any or all of these headers if including them would exceed any system environment limits.""" [1] http://hoohoo.ncsa.uiuc.edu/cgi/env.html P.S.: the link "http://cgi-spec.golux.com/draft-coar-cgi-v11-03.txt"; is broken.
[...]
Regards Manlio Perillo _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
