W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2011

Re: \-decoding filename parameters [general issue now #270]

From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Date: Fri, 4 Feb 2011 11:46:42 +0000
Cc: Mark Nottingham <mnot@mnot.net>, Adam Barth <ietf@adambarth.com>, httpbis <ietf-http-wg@w3.org>
Message-Id: <AEB542D3-B37A-4B72-BE79-CF4274BA3029@niven-jenkins.co.uk>
To: Julian Reschke <julian.reschke@gmx.de>
On 4 Feb 2011, at 11:13, Julian Reschke wrote:
> On 04.02.2011 11:40, Ben Niven-Jenkins wrote:
>> http://greenbytes.de/tech/tc2231/#attabspathwin
>> Firefox =>  \foo.html
>> Chrome =>  \\foo.html
>> Safari =>  \\foo.html
> But this is not; apparently those UAs consider "\" a legitimate character in a filename.
> I believe that's a very bad idea.

The handling of file names with a "\" in on Mac OS X is somewhat erratic.

You can save a file from a "GUI" application with \ in the fileanme, and at least some applications will open them (I only tried with TextEdit and MS Word) but while you can see them with an ls in a shell you get a "no such file/directory" error if you try access one. If you create a file with a \ in the filename from the shell the \ gets stripped out.

Firefox has some inconsistent behaviour - it won't open a file that starts with a \ and just presents a blank page but will open a file with a filename of the form foo\bar

I didn't try any other browsers.

Received on Friday, 4 February 2011 11:47:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:56 UTC