Graham Dumpleton wrote: > I am slowly working through what I think I at least need to do for > Apache/mod_wsgi. I'll give a summary of what I have worked out so far > based on the discussions and my own research. > ... > Next HTTP header to worry about is HTTP_REFERRER. > > There would be two parts to this, there would be the host name > component and then the path component. > > We already know from above that for unicode host name it should be the > IDNA name. > > For the path component, if the client follows the rules properly, then > if the path uses a non latin-1 encoding, then it should be using RFC > 2047 to indicate this so shouldn't have to do anything different and > use same rule as other HTTP headers. For this header we are actually > in a better situation that for URL in actual HTTP request line which > isn't so specific about encodings.
I don't think that's true. Referer must be absoluteURI or relativeURI, neither of which have defined encodings. RFC 2047 only applies to headers of type TEXT, of which there are surprisingly few. Robert Brewer fuman...@aminus.org _______________________________________________ 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
