More in this section
Forums / General Discussions / SFLB MIME type not set correctly

SFLB MIME type not set correctly

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. Mike
    Mike avatar
    208 posts
    10 Dec 2007
    09 Aug 2011
    Link to this post
    This is for Sitefinity 3.2, on IIS 6.

    I have two standard document libraries, both identical as far as I can tell, with caching set the same (cache until document is changed).

    On a page I've set up a link to each of the documents in one library, Both links were originally set with ?download=true.  When I click a link to one of the documents, I get the expected application/x-download and I can download the file.

    When I change this, so that the PDF opens in the browser window instead of downloading (remove the download querystring, and set target="_blank"), and click a link to the document, I get this response from Firefox, saying:  "you have chosen to open <document name> which is a SFLB file..."  See attachment "no mime type.png"

    What's odd here is that in the case of this document library, using Internet Explorer or Firefox on different machines, one link now works correctly, and the other link does not.

    Now, in the other document library, a PDF was uploaded, but the link on the page that points to the PDF did not have ?download=true and it opens in a new window as a PDF just fine.

    I'm assuming because of the odd behavior there is something wrong with the cache control headers, but I can't say for sure, since I've checked the links on another machine, and they behave the same way as the one I made the changes on.  In any case, the MIME type does not appear to be set correctly.

    Any suggestions?

    Mike Sharp
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    12 Sep 2017
    09 Aug 2011
    Link to this post
    Hi Mike,

    I remember that we had issues with this in 3.2 and I think with 3.5. You can try to upgrade to the latest SP of 3.5 or directly to 3.6 to see if this problem will be resolved. Actually you can make a new installation and check the behavior. Unfortunately the version you have is quite old and I cannot remember when exactly we fixed the issue and what was the actual problem.

    Best wishes,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
2 posts, 0 answered