Application Octet Stream Download
Always using MIME-Type 'application/octet-stream' is not optimal. Most if not all browsers will simply download files with that type. If you use proper MIME types.
I run a subscription-based site for poker training videos. In the recent past, some portion of our subscribers have developed problems downloading our videos. The affected users are exclusively seeing problems while using Chrome as their web browser, however there are other users who use Chrome with no problem.
Here is the exact behavior they are seeing:
- Pasting the url of a video file directly to their browser produces about:blank and the file does not download
- Clicking the link normally produces no result (e.g. it behaves like a dead link)
- Right-clicking the link and opening in a new tab/window produces about:blank and the file does not download
- Right-clicking the link and choosing Save-As produces a 5 to 10 second delay, after which they get a Save As dialog. After they choose a location, the download proceeds at full speed.
Again, this problem has only presented itself for a subset of users browsing with Chrome. All affected users have the latest version of Chrome, but so do some of the unaffected users. All affected users have Windows Vista or Windows XP. As far as we can tell (small sample size), none of the affected users have Windows 7 and none of our users on Windows 7 have been affected.
What could be causing this problem? How could it be solved?
Javascript Application Octet Stream
Edit: Here is a copy of the headers from one of these downloads.
Edit: Some updates. Chrome extensions do not seem to affect this. One of the affected systems was upgraded from Windows XP to Windows 7, with no other changes made. That system now downloads properly. This issue doesn't only affect the WMV videos. It happens with FLV and M4V as well. A sample file is at http://www.grinderschool.com/videos/zbn9Y7TbeWcUbCPFNnLd/Carroters001.wmv
3 Answers
You are sending the Content-Type: application/octet-stream header, presumably hoping to trigger the browser to download the file instead of letting the user view it. This however is not really the best way. You are better of with sending the correct content type and add a content disposition header, like so:
How to send this header depends on your server platform.
Google Chrome uses the Safe Browsing API by default (blog post here). The Safe Browsing API maintains a list of potentially malicious sites. It is possible that the page has been flagged as malicious. Google offers another tool called Webmaster Tools that allows the webmaster to verify ownership of a site through a review process, then mark a site as not malicious (details here).
At a minimum, you could start by adding the site in Webmaster Tools and checking under Diagnostics --> Malware to see if it has been added as a malicious site.
I would highly suggest to try to use another video encoding such as MPEG, OGG/OGV, WebM and perhaps a Flash fallback. In fact, it would be best to give alternative choices to the user. Modern browsers are going to be focusing on the HTML5 standard. So have a look at how you can manage the different video codecs in HTML5.
A Windows Media Video (WMV) file is proprietary to Microsoft and some users might not have the Windows Media Player plugin for Chrome.
From Google Answers:
If a page simply links to Windows media files (e.g. .asf or .asx files), you might not see a prompt to download the Windows Media Player plug-in.
Application Octet Stream Download
Also, you may want to check if there is any difference when the links ar absolute or relative.
Octet Stream Download
