User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040720 I recently emailed a file to myself using Yahoo! email. The filename was "A file with spaces in the filename.dat". When I used Mozilla Firefox to download it and clicked "save to disk" the filename was truncated to "A". I downloaded the latest build of Mozilla and the problem still exists. Incidentally, I was able to download the file and get the correct filename using Opera. Reproducible: Always Steps to Reproduce: 1. visit http://mail.yahoo.com/ Enter "firefox_test_acct" as the login name and "mozilla" as the password. 2. Click "inbox" 3. Click on "mozilla email bug proof of concept" to load the email which demonstrates the problem. 4. Scroll down and click on "Scan and Download Attachment" for "A_file_with_spaces_in_the_filename.dat". Note that while Yahoo! email appears to have inserted underscores in place of the spaces, when I download this file with Opera, the spaces are there, not underscores. 5. Click "Download Attachment" 6. Note that the window that pops up says "Opening A. The site has suggested that "A" can be handled...", but the filename in the email is "A file with spaces in the filename.dat" 7. Feel free to try to download "Another file with spaces in the filename.dat". Mozilla will save it as "Another". Actual Results: The expected filenames were truncated at the first space in the filename. Expected Results: It should allow downloads of files from Yahoo! even if they have spaces in the filename. I think this bug is similar to bug #243856, but I can't be sure since the original poster of that bug couldn't reproduce the problem.

The problem is that yahoo does not properly escape the spaces in the HTTP headers it sends... Over to evangelism. We used to do what Opera does, but doing that while supporting filenames in no-Western languages is basically impossible, so we've moved to actually following the standard.

Same as bug 221028? That was wontfix.

Same issue, but that bug was not filed on a particular site, so there was nothing to evangelise. Here, there's a site to evangelise.

*** Bug 255732 has been marked as a duplicate of this bug. ***

*** Bug 243856 has been marked as a duplicate of this bug. ***

*** Bug 264639 has been marked as a duplicate of this bug. ***

*** Bug 270063 has been marked as a duplicate of this bug. ***

I hate to point this out but even if this is a problem with Yahoo, IE seem to handle it correctly and identifies the whole file name. The chances of ever getting Yahoo to fix anything seem to be close to nil so if there is anyway for Mozilla and Firefox to deal with this I vote for it.

(In reply to comment #8) > I hate to point this out but even if this is a problem with Yahoo, IE seem to > handle it correctly and identifies the whole file name. We know it, see the bug in comment 2.

*** Bug 271255 has been marked as a duplicate of this bug. ***

*** Bug 271519 has been marked as a duplicate of this bug. ***

*** Bug 272850 has been marked as a duplicate of this bug. ***

why dont all of us send emails to yahoo feedback? http://add.yahoo.com/fast/help/au/mail/cgi_feedback?from_url=http://help.yahoo.com/help/au/mail/errors/errors-11.html so they get the idea that a lot of its users are having this probelm. i have sent mine, and they said they will look at this. maybe the more complaints, they will pay more attention?

In Japanese Yahoo! e-mail, this issue is more serious. All Japanese characters get corrupted in attachment file name. For instance, a Japanese attachment file name represented as "0x83 0x65 0x83 0x58 0x83 0x67.txt" in hexadecimal format get currupted like "0x5F 0x65 0x5F 0x58 0x5F 0x67.txt". The 1st byte of each multi-byte character is currupted. I am unsure about other languages but guess something similar happens.

*** Bug 274359 has been marked as a duplicate of this bug. ***

*** Bug 250441 has been marked as a duplicate of this bug. ***

This is not just an yahoo issue. The Technical Director of my Company had the Problem with several download portals of related Companys. This is confirmed by the tech staff from different PC and OS configurations (Linux,FreeBSD,Win32) and Firefox 1.0

dbemerlin@gmx.de, The engineer responsible for this area of code decided in bug 221028 comment 6, that this was the result of faulty, buggy server side code which we would not attempt to work around due to other potential problems which might occur. You may disagree and say that we should "do as IE does", but the whole point is _we follow the specifications for a reason_ which helps us resist many of the problems that plague IE.

*** Bug 281976 has been marked as a duplicate of this bug. ***

This must be a firefox issue. I have the same problems, my attachments are truncated and there is not .*** filetype when I download. I forwarded the message from my yahoo account to one that I check with Thunderbird, and all is good. Why is it that Thunderbird gets it right, but Firefox does not?

*** Bug 283682 has been marked as a duplicate of this bug. ***

*** Bug 287572 has been marked as a duplicate of this bug. ***

*** Bug 292034 has been marked as a duplicate of this bug. ***

*** Bug 294757 has been marked as a duplicate of this bug. ***

*** Bug 294811 has been marked as a duplicate of this bug. ***

*** Bug 296392 has been marked as a duplicate of this bug. ***

*** Bug 293037 has been marked as a duplicate of this bug. ***

Apart from a small catch. You are supposed to stick to the 'correct' way of doing things as opposed to what everybody else does, mainly in order to be able to handle correctly non-western filenames. If this is the case, despite the grievances about the underscores, the spaces and exotic characters like square brackets, I should at least be able to see Greek filenames. The trouble is that I see neither. Which means that there must be something fundamentally wrong with your code. If the problem restricted itself to just spaces, I might say there is something wrong in the way Yahoo handles headers (whatever this might be!!!). Brackets, however, and underscores are plain vanilla ASCII characters. So why them? Don't you think it is a totally ridiculous situation that thousands and thousands of people should be made to send their mails to their provider accounts just in order to be able to download attachments properly with Thunderbird? Sorry this note is a bit outspoken, but what we're asking for is your mercy, after all!

Not just with email attachments on yahoo but any site where it directs to a file that the browser will download instead of view directly will truncate to the first space. If it opens directly in the browser, for example a .jpeg, it comes up fine unless you download.

*** Bug 298574 has been marked as a duplicate of this bug. ***

*** Bug 300732 has been marked as a duplicate of this bug. ***

*** Bug 304438 has been marked as a duplicate of this bug. ***

I filled in a feedback form on Yahoo Mail a while back, including a link to this bug, which was answered by Yahoo on 31 August. As of today, Yahoo seem to have fixed it! The HTTP response now has quotes around the filename, so spaces, underscores, etc are no longer a problem.

wow, thanks reptar! marking fixed. Thanks Nate!