Closed
Bug 66181
Opened 24 years ago
Closed 24 years ago
Content-Disposition filename with quotes is parsed wrong
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
VERIFIED
FIXED
mozilla0.9
People
(Reporter: stas-bugzilla, Assigned: darin.moz)
Details
(Keywords: verifyme)
Attachments
(1 file)
823 bytes,
patch
|
Details | Diff | Splinter Review |
When I use Content-Disposition header for HTTP response, and give a filename as a quoted string (according to RFC2183, filename can be given as filename=value, where value is token or quoted-string), the file that user gets offered for downlaod, contains double quotes. I think Mozilla should detect this situation and strip the quotes. Test case: connect with Mozilla to a socket, and give as a response header: HTTP/1.1 200 OK Content-type: application/x-msdos-program Content-Disposition: inline; filename="test.txt" Content-Length: 20 Connection: close You will see that you are offered to download file "test.txt" - with quotes!
Assignee | ||
Updated•24 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee | ||
Comment 3•24 years ago
|
||
Assignee | ||
Comment 4•24 years ago
|
||
Scott, can you r/sr this patch? Thanks!
Comment 6•24 years ago
|
||
*doh* that's my bad. thanks darin. sr=mscott
Assignee | ||
Comment 7•24 years ago
|
||
Patch checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
+verifyme: Tom, do you think our customizable HTTP test server can do this?
Keywords: verifyme
Comment 9•23 years ago
|
||
Ben, yeah, the internal testcase is 01ContentDisposition verified: 6/27 branch and trunk, all platforms
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•