221708 - file handling APIs fail to deal with non-ascii extensions

Status: RESOLVED DUPLICATE of bug 80787

(Core Graveyard :: File Handling, defect)

Description

[Christian :Biesinger (don't email me, ping me on IRC)]

http://lxr.mozilla.org/seamonkey/source/netwerk/mime/public/nsIMIMEInfo.idl#64
http://lxr.mozilla.org/seamonkey/source/uriloader/exthandler/nsIExternalHelperAppService.idl

all of those use |string| for extensions. better would be AString or wstring, so
that the APIs support non-ascii characters.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Quite frankly, do these come up?

What charset do we assume the extension from nsIURL is in?

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

>Quite frankly, do these come up?

if a server sends them... I haven't seen any yet, but they aren't prohibited.
also if an application decides to use them, but I haven't seen such an
application either

>What charset do we assume the extension from nsIURL is in?

ASCII, it seems. at least we pass it through |string| parameters. On the other
hand, we don't unescape it.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

(In reply to comment #1)
> Quite frankly, do these come up?

apparently, at one time you were convinced of that ;)

*** This bug has been marked as a duplicate of 80787 ***