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 r.david.murray
Recipients eric.araujo, orsenthil, pitrou, r.david.murray
Date 2010-10-12.17:23:22
SpamBayes Score 6.5872214e-09
Marked as misclassified No
Message-id <1286904206.64.0.307761386147.issue10063@psf.upfronthosting.co.za>
In-reply-to
Content
Éric: Well....I suppose that depends on how you look at it.

The RFC says that 'file:' does not specify a network protocol, and so "it's utility in network protocols between hosts is limited".  So, technically an implementation that decides to handle 'file://<fqdn>' by using ftp isn't *wrong*, but it certainly isn't something that someone writing a 'file:' uri should expect to work.

I agree with Senthil, I am -1 on backporting this to earlier versions because of the potential for breaking "working" applications (even though those applications shouldn't really be working :)

Antoine: except that the RFC allows FQDNs in 'file:' URIs.  So I don't think we can just reject them.
History
Date User Action Args
2010-10-12 17:23:26r.david.murraysetrecipients: + r.david.murray, orsenthil, pitrou, eric.araujo
2010-10-12 17:23:26r.david.murraysetmessageid: <1286904206.64.0.307761386147.issue10063@psf.upfronthosting.co.za>
2010-10-12 17:23:22r.david.murraylinkissue10063 messages
2010-10-12 17:23:22r.david.murraycreate