Jump to content

Recommended Posts

Posted

Anyone know anything about how IE11 (and Chrome as well) handles MIME types?

 

We host a local intranet server on IIS6.1 - which is a searchable file store. Any file downloads are presented to the user as an http://Http://server/path/filename.extension so they can right click to save, or click to open directly (if supported - for pdf/word files etc)

 

The problem we are having is that a lot of file extensions are related to a specific app (.qxp for quark for example) and these links don't work. When clicked they open a blank tab in IE, or generate a failed download in Chrome. I've specified additional MIME types in IIS as application/octet-stream for these and its worked - but not for all of the extensions! I've also put a default MIME type (.*) of application/octet-stream but this doesn't seem to have any affect.

 

Example, a file extension of .plf or .dtd is opened as xml - when it should prompt for a download. Both have MIME types in IIS as application/octet-stream. The same setup for .qxp has worked fine however!

 

Am I missing something, or do I need to make changes to something else in IIS, or group policy (although this affects all users, on all PCS so I'm assuming its more IE/Chrome or IIS related)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...