Message 84260 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	jhylton
Recipients	dmahn, jhylton
Date	2009-03-27.14:50:55
SpamBayes Score	0.0030130567
Marked as misclassified	No
Message-id	<1238165457.43.0.269176969831.issue5468@psf.upfronthosting.co.za>
In-reply-to

Content
Indeed, I think I confused some other character encoding issues related to HTTP with the URI issue. The discussion in RFC 3986 is length and only occasionally clarifying for this issue. That is, it doesn't say anything definitive like applications are free to use any character encoding when decoding a URI. But I think it agrees with your assessment that an application is free to interpret the binary data however it wants, e.g. http://tools.ietf.org/html/rfc3986#section-2.1

Indeed, I think I confused some other character encoding issues related
to HTTP with the URI issue.  The discussion in RFC 3986 is length and
only occasionally clarifying for this issue.  That is, it doesn't say
anything definitive like applications are free to use any character
encoding when decoding a URI.  But I think it agrees with your
assessment that an application is free to interpret the binary data
however it wants, e.g. http://tools.ietf.org/html/rfc3986#section-2.1

History
Date	User	Action	Args
2009-03-27 14:50:57	jhylton	set	recipients: + jhylton, dmahn
2009-03-27 14:50:57	jhylton	set	messageid: <1238165457.43.0.269176969831.issue5468@psf.upfronthosting.co.za>
2009-03-27 14:50:56	jhylton	link	issue5468 messages
2009-03-27 14:50:55	jhylton	create