urls and %nn encoding

[Kevin Bullock]

On 17 Jan 2012, at 7:21 PM, Mads Kiilerich wrote:

> Following up on http://markmail.org/message/olyscnnw7nn5e7sd :
> 
> What kinds of 'urls' should %nn encoding apply to?
> 
> urls.txt does not give a clear answer, and we do not strictly follow the RFCs.
> 
> It would be reasonable to expect that 'hg clone http://server/foo%20bar' created './foo bar/' locally (issue3145).

Yes.

> It is perhaps also reasonable that 'hg clone /tmp/foo%20bar' creates './foo%20bar/'.

Yes, since that's not a URL. The URL form would of course be 'file:///tmp/foo%2520bar/'. ;)

> But what path should 'hg clone file:///tmp/foo%20bar' clone from and to?

Ideally, it should clone from '/tmp/foo bar' to './foo bar' (per RFC 1738). I say 'ideally' because I'm not sure what the impact on current users would be. But if we can reasonably make our URL handling follow the RFC, I'm of the opinion that we should.

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20120117/6dbc66d5/attachment-0002.html>