User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Build ID: 20120215223356 Steps to reproduce: Took the recent stable channel update to Firefox 12.0 under Windows. Keep using Outlook Web Access Version 14.1.355.2 (OWA). Tested on two different Windows machines. Already commented on Bug 703015 . Filing a new one since that one is closed. Actual results: Individual attachments are now all saved as bttachment.<extension> or as bttachment.ashx for some reason. The file name is rubbish. However the <extension> is sometimes fine, .pdf for example, but .ashx is used. It appears that for attachments where the extension is fine, it seems to be always fine. Where it is .ashx, it is always that. Expected results: Attachments should have the proper file names they carry. I am aware that this might be a problem in OWA.

Could you provide the headers for an OWA attachment download request as in https://bugzilla.mozilla.org/show_bug.cgi?id=703015#c31 please?

When did this start happening for you? This was fixed and verified in Firefox 9 and 10.

It was fine with Firefox 11, and right after the update to Firefox 12.0 it startet.

One more remark, I cannot really speak for the former Firefox versions, but I know that it was fine before the update to 12.0, If possible someone should test it in Firefox 11 as well. I could do that, but currently I do not know how to go backwards in the stable channel.

Andrea, have you ever seen OWA return to "filename*" parameters? It this somehow new?

(In reply to Sven Ludwig from comment #6) > One more remark, I cannot really speak for the former Firefox versions, but > I know that it was fine before the update to 12.0, If possible someone > should test it in Firefox 11 as well. I could do that, but currently I do > not know how to go backwards in the stable channel. Sven, I don't believe we had any functional changes in Content-Disposition handling since Firefox 10. You may want to try the ESR stream to check this.

I did the test and "upgraded" to Firefox 10.0.4 ESR using the installer for British English, and I get the same results. The filenames are screwed in the above described way.

(In reply to Sven Ludwig from comment #9) > I did the test and "upgraded" to Firefox 10.0.4 ESR using the installer for > British English, and I get the same results. The filenames are screwed in > the above described way. So are you still sure this has anything to do with the FF version? From the response headers, it seems more likely that a proxy is messing with OWA's response.

I can't reproduce this using Fx12 (Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0) and the same version of OWA (14.1.355.2). What I get in the response header is: Content-Disposition:attachment; filename*="SomeReasonableFilename.JPG" without the extra filename*=UTF-8''bttachment.ppt parameter that appears in Sven's attachments, so I agree with Julian that maybe someone's messing up with the headers. Sven, can you try the same download request without passing through a proxy (in case you're currently going through one)? Please let me know if there are further investigations I can carry on.

Ok, thank you for the analysis, Andrea. I was never sure whether it was a problem that could be fixed in the browser, in OWA, or something else. It might be a weird problem in the specific environment in which I use OWA, and its occurence somehow coincided with the Firefox update. Feel free to close the bug at this point. ;-)

resolving as WFM based on Comment 12.