➜

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 orsenthil
Recipients orsenthil
Date 2010-10-10.09:40:16
SpamBayes Score 0.00012145838
Marked as misclassified No
Message-id <1286703624.02.0.46805329948.issue10063@psf.upfronthosting.co.za>
In-reply-to
Content 
file:// scheme should not be allowed to access a file on remote machines.  RFC 1738, says that host, if present should be the FQDN of the machine, but relaxing on that I thinking that localhost and its variants should okay as long as it is the local machine.

What is going to break in 3.2 is file:// trying to access resources on remote machine via FTP, which it is currently trying to do.

Attached is patch to accomplish this.(NEWS and Docs will be added).

This would introduce a regression, so this may not be backported.
History
Date User Action Args
2010-10-10 09:40:24orsenthilsetrecipients: + orsenthil
2010-10-10 09:40:24orsenthilsetmessageid: <1286703624.02.0.46805329948.issue10063@psf.upfronthosting.co.za>
2010-10-10 09:40:20orsenthillinkissue10063 messages
2010-10-10 09:40:20orsenthilcreate