Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
OWA 2010 Attachments Download as *.ashx

Answered OWA 2010 Attachments Download as *.ashx

  • Wednesday, November 16, 2011 5:03 AM
     
     
    Sign In to Vote
    2

    Hello,

        We have been using OWA 2010 in our organization for a few months now and have not had any issues up until now. Firefox 8 was just released, and with that update, the attachment function in OWA 2010 is not working as expected.

        The issue is when you download an attachment, it always downloads as attachment.ashx. I have tracked this down to a malformed Content-Disposition header. OWA is sending the following Content-Disposition:

        Content-Disposition: attachment; filename*="FILENAME.EXT"

        This notation *= is referenced in the RFC 2231 Standard, but with one notable difference:

        Content-Disposition: attachment; filename*=''FILENAME.EXT

        Please note that the '' above are two single quotes, and would enclose the language 'en-ca' and if specifying a content type UTF8'en=ca' making the above:

        Content-Disposition: attachment; filename*=UTF8'en-ca'FILENAME


        I have tested this using PHP to send the malformed headers to the browser and have confirmed that this is the behaviour of the browser when the malformed headers are received. This was tested with both Firefox 8 and Internet Explorer 9 too. Internet Explorer 9 actually does not support this notation at all. It requires the following Content-Disposition:

        Content-Disposition: attachment; filename=FILENAME

        You drop the single and double quotes as well as the content type and language.

        Does anyone know of a patch or fix for this? I read somewhere that Update Rollup 1 was supposed to have addressed what I think was the same problem, however, we are already at Update Rollup 3 or 4.

        I know we could downgrade the browsers or rename the files upon download to work-around the problem, but would prefer to find a solution, not a work-around ;-)

        Any Ideas?

    Cheers,
    titanicfanatic

     

All Replies

  • Wednesday, November 16, 2011 9:20 AM
     
     
    Sign In to Vote
    0
    We have the same problem :(
     
  • Thursday, November 17, 2011 2:21 PM
     
     Answered
    Sign In to Vote
    0

    I'm also having this problem with Update Rollup 5 installed.

    Currently telling my users to use IE8 as a work-around, but would really appreciate a solution.

     
  • Monday, November 21, 2011 6:34 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    This has been reported as a product issue.

    Also we can find a lot discussion from http://support.mozilla.com/en-US/questions/895024

    I recommend you to use IE8 as a workaround first.

    Xiu

     

     
  • Friday, November 25, 2011 8:17 AM
     
     
    Sign In to Vote
    0
    Using IE isn't a workaround, we can't consider it. Now we are considering migrate from OWA to Google Apps with GMail. Thx.
     
  • Friday, December 02, 2011 9:08 AM
    Moderator
     
     Answered
    Sign In to Vote
    0
    Using IE isn't a workaround, we can't consider it. Now we are considering migrate from OWA to Google Apps with GMail. Thx.


    Hi,

    Bug that has been report from firefox,too.

    Outlook web access attachments download as .aspx

    https://bugzilla.mozilla.org/show_bug.cgi?id=703015

    You can contact Microsoft to ask for intern fix for this issue.

    Xiu Zhang

    TechNet Community Support

     
  • Friday, December 02, 2011 9:13 AM
     
     
    Sign In to Vote
    0

    No, it isn't a Firefox bug, as you can read in bugzilla, that's a Firefox workaround to allow OWA to use bad headers. The real fix have to come from Microsoft.

    Where can I contact Microsoft?

    Thx

     
  • Friday, December 02, 2011 9:22 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    You can use the URL below:

    https://support.microsoft.com/oas/default.aspx?&sd=gn&c1=508&gprid=13965&&st=1&wfxredirect=1

    Xiu Zhang

    TechNet Community Support

     
  • Friday, December 02, 2011 11:39 PM
     
     
    Sign In to Vote
    0

    Hello Xiu Zhang,

    > This has been reported as a product issue.

    Good, this means Microsoft is already aware of this problem and working an a fix?

    > You can contact Microsoft to ask for intern fix for this issue.

    Is an internim fix already avaiable? If so, how can i request such an internim fix for my Exchange 2010 installation? Can you send me an E-Mail or instructions?

    It´s seldom for me to require internim fixes for Microsoft Software, last time was Years ago and for Windows Server 2003, for that issue back then there was a KB article and had to request that specific fix per E-Mail. That was quite easy then.

    With kind regards,
    John

     
  • Monday, December 05, 2011 5:42 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi John,

    I do not ave that template. You may have a look at the article below, you can call 1-800-936-4900 to have a help.

    http://msmvps.com/blogs/bradley/archive/2005/02/15/36033.aspx

    Xiu Zhang

    TechNet Community Support

     
  • Monday, December 12, 2011 11:50 PM
     
     
    Sign In to Vote
    0

    Hello titanicfanatic,

    Thank you for reporting the issue. Firefox 8 has a change that enforces some parts of RFC 2231 (https://developer.mozilla.org/en/Firefox_8_for_developers#Network) - in particular it no longer accepts double quotes as delimiters within MIME parameters.

    Unfortunately, this change broke Outlook Web App. We are aware of this issue and are working on the fix.

    If you would like to track the status of the issue, please contact Microsoft support.

     
  • Wednesday, January 18, 2012 5:26 PM
     
     
    Sign In to Vote
    0
    Upgraded to Firefox 9.0.1 and the issue appears to be gone again...
     
  • Wednesday, January 18, 2012 6:03 PM
     
     
    Sign In to Vote
    0
    Yes, because we backed out the change for now. Hopefully OWA will be fixed soon, so that we can put it back in.
     
  • Sunday, April 22, 2012 8:25 PM
     
     
    Sign In to Vote
    0
    Out of curiosity: has this been fixed in OWA in the meantime?