User Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Build ID: 20111220165912 Steps to reproduce: In our organization we use OWA (Exchange 2010) as email client using Firefox. Actual results: We have updated to Firefox 9.01. Expected results: All attachments came as "attachment.ashx" and we're unable to download them with the real file name and extension.

There was bug 703015 but that was fixed for Firefox 9.... What Service Pack / Update Roll-up are you running on Exchange 2010?

>We have updated to Firefox 9.01 and from which Version do you ugraded ?

Can't reproduce with: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 using OWA 2010 v. 14.1.355.2

We are running OWA on Exchange Server 2010 vers. 14.01.0289.001. Updated Firefox to vers. 9.01 from Firefox vers. 7.

(In reply to s.serrotti from comment #4) > We are running OWA on Exchange Server 2010 vers. 14.01.0289.001. > Updated Firefox to vers. 9.01 from Firefox vers. 7. That looks to be Update Rollup 3 for Exchange Server 2010 SP1 -> any chance you can get updated to Exchange Server 2010 Service Pack 2

Reporter -> Any update? Does this still happen with Firefox 10.0.2? Any luck getting Exchange updated to the latest service pack?

I apoligize for not having updated this thread since 2012-01-16. The problem has been solved when I installed the update rollup 6 for Exchange Server 2010 SP1 (KB2608646). Many thanks.

(In reply to s.serrotti from comment #7) > I apoligize for not having updated this thread since 2012-01-16. > > The problem has been solved when I installed the update rollup 6 for > Exchange Server 2010 SP1 (KB2608646). > > Many thanks. I'm confused; I thought that predates the whole discussion. Are you really sure this wasn't fixed by Firefox 9?

Yes I'm sure. The problem wasn't fixed by Firefox 9, but CAUSED by Firefox 9. We started to experience this problem just when we updated from Firefox 7 to Firefox 9.01 as you can see in my previous post 2012-01-13 00:29:35 and 2012-01-16 00:57:23.

(In reply to s.serrotti from comment #9) > Yes I'm sure. The problem wasn't fixed by Firefox 9, but CAUSED by Firefox > 9. We started to experience this problem just when we updated from Firefox 7 > to Firefox 9.01 as you can see in my previous post 2012-01-13 00:29:35 and > 2012-01-16 00:57:23. No, it started in Firefox 8 and was fixed in Firefox 9.

Ok, I believe what you say, bat in OUR case this isn't what has happened. Anyway, the problem has been solved, many thanks for your help. Have a nice day.