Message 239106 - 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	chrysn
Recipients	chrysn
Date	2015-03-24.10:45:13
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1427193914.26.0.435634285689.issue23759@psf.upfronthosting.co.za>
In-reply-to

Content
The CoAP protocol (RFC 7252) registers the new URI schemes coap and coaps. They adhere to the generic RFC3986 rules, and use netloc and relative URIs. Therefore, please add the 'coap' and 'coaps' schemes to the uses_relative and uses_netloc lists in urllib.parse. I'm not sure about uses_params; the CoAP protocol in itself does not do anything special with the ';' character in URIs, so probably it should not be included there. (But then again, neither does RFC2616 mention ";" in the context of addresses, and it is included in uses_params).

The CoAP protocol (RFC 7252) registers the new URI schemes coap and coaps. They adhere to the generic RFC3986 rules, and use netloc and relative URIs.

Therefore, please add the 'coap' and 'coaps' schemes to the uses_relative and uses_netloc lists in urllib.parse.

I'm not sure about uses_params; the CoAP protocol in itself does not do anything special with the ';' character in URIs, so probably it should not be included there. (But then again, neither does RFC2616 mention ";" in the context of addresses, and it is included in uses_params).

History
Date	User	Action	Args
2015-03-24 10:45:14	chrysn	set	recipients: + chrysn
2015-03-24 10:45:14	chrysn	set	messageid: <1427193914.26.0.435634285689.issue23759@psf.upfronthosting.co.za>
2015-03-24 10:45:14	chrysn	link	issue23759 messages
2015-03-24 10:45:13	chrysn	create