773542 - PDF's fail to download correctly - failure is when spaces are in file name

Status: RESOLVED DUPLICATE of bug 221028

(Core :: General, defect)

Description

[Phil Wyatt]

Attachment: Firefox glitch.pdf

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
Build ID: 20120614114901

Steps to reproduce:

We have an internal intranet application that produces PDF files. When these are downloaded in Firefox we get a spurious result when the file names have spaces in them. They do not get the .pdf extension and therefore they are not recognised as pdf's


Actual results:

When these are downloaded Internet Explorer and Safari both download them correctly and show the names complete with spaces and the .pdf extension however Firefox fails at the first "space" and then as there is no extension they are not recognised as pdf's and the user has to select the required program to open the file.


Expected results:

The full name of the pdf and the extension should show in the download

Comment 1

[Phil Wyatt]

We are in the process of removing the spaces in our internal application however this does seem like a bug that could affect many people.

Comment 2

[Boris Zbarsky [:bzbarsky]]

What exact headers are you sending?  Per spec, filenames with spaces in them are supposed to be placed in double quotes.  Are you doing that?

Comment 3

[Phil Wyatt]

I will check with the developers - has this changed recently because it works in earlier versions of firefox (V9)?

Comment 4

[Boris Zbarsky [:bzbarsky]]

Hmm. Julian?

Comment 5

[Julian Reschke]

Test case: http://greenbytes.de/tech/tc2231/#attwithasciifilenamenqws

As far as I know, it has always been like this. I would recommend not to change anything here to be more permissive; next people will ask for "," or ";" not to be treated as delimiters. People really need to fix their code to use the correct syntax.

Comment 6

[Phil Wyatt]

My apologies - just checked on older version and its the same. I will get our developers to make the required changes.

Keep up the good work

Comment 8

[Julian Reschke]

I believe this bug can be closed.

Comment 9

[Stefan Weiss [:sir_none]]

closed, because it was not an firefox bug

feel free to reopen if you feel this is not correct and you have additonal information for us.

thanks for the help to make firefox better.