Hi Zack, there are http URL. WCCP redirection on ASA is configured only for port TCP/80. HTTPS connections (TCP/443) goes directly to internet. Content type 'application/octet-stream' will always cause Firefox to show the 'open with' download dialog. To avoid this download you would have to configure the server to send another content type and possibly change the file extension of the file.
MIME types describe the media type of content, either in email, or served by web servers or web applications. They are intended to help provide a hint as to how the content should be processed and displayed.
Examples of MIME types:
text/html
for HTML documents.text/plain
for plain text.text/css
for Cascading Style Sheets.text/javascript
for JavaScript files.text/markdown
for Markdown files.application/octet-stream
for binary files where user action is expected.Server default configurations vary wildly and set different default MIME-type values for files with no defined content type.
Versions of the Apache Web Server before before 2.2.7 were configured to report a MIME type of text/plain
or application/octet-stream
for unknown content types. Modern versions of Apache report none
for files with unknown content types.
Nginx will report text/plain
if you don't define a default content type.
As new content types are invented or added to web servers, web administrators may fail to add the new MIME types to their web server's configuration. This is a major source of problems for users of browsers that respect the MIME types reported by web servers and applications.
If a web server or application reports an incorrect MIME type for content (including a 'default type' for unknown content), a web browser has no way of knowing the author's intentions. This may cause unexpected behavior.
Some web browsers, such as Internet Explorer, try to guess the correct MIME type. This allows misconfigured web servers and applications to continue working for those browsers (but not other browsers that correctly implement the standard). Apart from violating the HTTP spec, this is a bad idea for a couple of other significant reasons:
text/html
or text/plain
in order to have the documents either processed and displayed as HTML or as source code. If the browser guesses the MIME type, this option is no longer available to the author.When looking for information about JavaScript MIME types, you may see several MIME types that reference JavaScript. Some of these MIME types include:
application/javascript
application/ecmascript
application/x-ecmascript
application/x-javascript
text/ecmascript
text/javascript1.0
text/javascript1.1
text/javascript1.2
text/javascript1.3
text/javascript1.4
text/javascript1.5
text/x-ecmascript
text/x-javascript
While browsers may support any, some, or all of these alternative MIME types, you should only use text/javascript
to indicate the MIME type of JavaScript files.
Note: See MIME types (IANA media types) for more information.
There are several ways to determine the correct MIME type value to be used to serve your content.
Content-Type
header.Content-Type
and it will report the content type of the resource.<meta>
element in the page source that gives the MIME type, for example <meta http-equiv='Content-Type'>
.<meta>
element that specifies the MIME type should be ignored if there's a Content-Type header available.IANA keeps a list of registered MIME Media Types. The HTTP specification defines a superset of MIME types, which is used to describe the media types used on the web.
The goal is to configure your server to send the correct Content-Type
header for each document.
.htaccess
equivalent tool, so all changes will go into the main configuration file.