[issue10063] file:// scheme will stop accessing via ftp protocol

Senthil Kumaran added the comment: Thanks for the comments and feedback. Fixed this in revision 85475. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker _

[issue10063] file:// scheme will stop accessing via ftp protocol

R. David Murray added the comment: I think the error message should be changed from 'allowed' to 'supported', though. -- ___ Python tracker ___

[issue10063] file:// scheme will stop accessing via ftp protocol

Éric Araujo added the comment: With this explanation, I agree with Senthil’s plan too. -- ___ Python tracker ___ ___ Python-bugs-list

[issue10063] file:// scheme will stop accessing via ftp protocol

R. David Murray added the comment: Éric: WellI 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://

[issue10063] file:// scheme will stop accessing via ftp protocol

Antoine Pitrou added the comment: (by disable I meant disallow, sorry) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue10063] file:// scheme will stop accessing via ftp protocol

Antoine Pitrou added the comment: I'd say disable hostnames in file:// URIs altogether. There's no practical reason for forcing a hostname in there, and trying to check that it matches the local host's FQDN sounds like a distraction. -- nosy: +pitrou _

[issue10063] file:// scheme will stop accessing via ftp protocol

Éric Araujo added the comment: Ah, I thought this was not a bug, because of “RFC 1738, says that host, if present should be the FQDN of the machine”. If it’s a bug I’m all for fixing it in all three versions. -- ___ Python tracker

[issue10063] file:// scheme will stop accessing via ftp protocol

R. David Murray added the comment: I doubt it. As Senthil says, file invoking ftp it is a bug. I'm just betting that *someone* is going to complain when it stops working in their particular situation. -- ___ Python tracker

[issue10063] file:// scheme will stop accessing via ftp protocol

Éric Araujo added the comment: file: URIs provoking FTP access seem wrong to me. Are there widely-used tools displaying this behavior? -- nosy: +eric.araujo ___ Python tracker ___

[issue10063] file:// scheme will stop accessing via ftp protocol

R. David Murray added the comment: If it's been reviewed on python-dev and the consensus was to turn it into an error in 3.2, then I'm fine with it. But I'll bet we'll get at least a few bug reports :) -- ___ Python tracker

[issue10063] file:// scheme will stop accessing via ftp protocol

Senthil Kumaran added the comment: On Sun, Oct 10, 2010 at 03:49:42PM +, R. David Murray wrote: > Does it also need a deprecation cycle? I think, adding a deprecation cycle might just delay this change. So, I would prefer if we make it in the 3.2 itself. - This is not a user-facing API cha

[issue10063] file:// scheme will stop accessing via ftp protocol

R. David Murray added the comment: Does it also need a deprecation cycle? -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-

[issue10063] file:// scheme will stop accessing via ftp protocol

New submission from Senthil Kumaran : 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 machin