417180 - Download Manager does not recognize space character

Status: UNCONFIRMED

(Toolkit :: Downloads API, defect)

Description

[Billium]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12

When trying to open or save a file that has a space character the download manager does not recognize the space and only saves the file as the characters that appear before the space character.
Example:
this file.pdf
Download manager attempts to open/save the file as "this" (without quotes)

This is frustrating when attempting to open files only, as they have to be saved with the correct extension and then opened.

Reproducible: Always

Steps to Reproduce:
1. Attempt to open/save a file with spaces in the file name
2. Download Manager attempts to open/save the file using only the string before the space; therefore, the file extension is unknown
3. File must be renamed and saved to disk with the correct file extension manually typed
Actual Results:  
The file is downloaded successfully but cannot be opened without saving to disk and taking the the correct "Steps to Reproduce"

Expected Results:  
Download Manager should recognize the space character so that files can be opened without saving to disk.

Internet Explorer does not have this problem.

Comment 1

[WADA:World Anti-bad-Duping Agency]

Phenomenon you are reporting can occur, if server is not compliant with RFC.
> Content-Disposition: ... filename=this file.pdf
This header means filename="this". ('file.pdf' is merely a comment) 
If filename="this file.pdf", file name have to be quoted by '"'. 
> Content-Disposition: ... filename="this file.pdf"

This case, isn't it?
 

Comment 2

[mikitemp]

No, this is not the case. I confirm this bug.
I checked the html code of one download page and there is the ".  (it's like: filename="this file.pdf").

This bug is present in all versions of Firefox ('till 3.5.4), also on Macintosh and Windows platform.

IE, Safari and Chrome do not have this problem.

mk

> Phenomenon you are reporting can occur, if server is not compliant with RFC.
> > Content-Disposition: ... filename=this file.pdf
> This header means filename="this". ('file.pdf' is merely a comment) 
> If filename="this file.pdf", file name have to be quoted by '"'. 
> > Content-Disposition: ... filename="this file.pdf"
> 
> This case, isn't it?
>

Comment 3

[Stuart Langridge]

As a data point, this happened to my parents today. They were attempting to download a document with header

Content-Disposition: attachment; filename=SV1 latest version.docx;

and this was being saved as "SV1". Since it's a docx file, it's also a zip file, and so their machine was then opening the downloaded file with an archive manager, not a word processor. Certainly according to the spec that header is incorrect (the filename should be quoted, since a single token can't contain separators, including spaces). However, it might be useful for Firefox to do the helpful rather than correct thing in this case?