[Webkit-unassigned] [Bug 144320] URL paths should not be normalized when encoded

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=144320

--- Comment #15 from Darin Adler <darin at apple.com> ---
(In reply to comment #14)
> Updated patch to do the normalization or not depending on the platform. Also
> removed the form data filename, as I'm not sure about that case. Darin, is
> it correct to assume that PLATFORM(COCOA) means HFS?

It’s not correct to assume that. Macs support NFS, for example.

It’s true that most older Unix systems have filenames that are an arbitrary string of bytes; the typical restriction is simply that none of the bytes can be '\0' or '/'. But note that the string of bytes can’t necessarily be converted into a sequence of UTF-16 code points. There could easily be a filename that’s not a valid UTF-8 sequence. How would we handle that?

When we are talking about URLs, what matters is the file system on the server, not on the client.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150722/32572d6c/attachment.html>