Closed Bug 149018 Opened 23 years ago Closed 23 years ago

browser doesn't respect national chars in content-disposition header

Categories

(Core Graveyard :: File Handling, defect)

Product:
Core Graveyard
Component:
File Handling
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: aha, Assigned: law)

Details

Browser doesn't respect national chars setted as file name using Content-disposition in HTTP header and offers to save file without them Example: Content-Disposition: inline; filename=text_è.html will offer name text_.html 2002060308/trunk/W2K (If filename in Content-Disposition have to be ASCII, mark this bug as INVALID.)
dupe of bug 147333 ?
Probably yep. Marking dupe. *** This bug has been marked as a duplicate of 147333 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Oops, bug 147333 is just for Sun/Solaris, so this is not dupe of that bug. REOPEN
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
See http://lxr.mozilla.org/seamonkey/source/uriloader/exthandler/nsExternalHelperApp Service.cpp#894 which cites the exact RFC and section that specifies that the filename must be ASCII.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → INVALID
v=aha (Thanx Boris for pointing)
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.