When IIS locates a file that does not have an extension, the Content-Type that is sent back to the browser is set to application/octet-stream.

1. How To Open Application Octet Stream File
2. How Do You Open Application/octet-stream
3. How To Open Octet-stream File Online
4. Mime Application Octet Stream

Some scanners mail the scanned pdf file as an application/octet-stream with pdf extension. These are indeed pdf files.

Currently, they are not opened as pdf, but I get the application chooser dialog, because no application is associated to application/octet-stream. I would like the system to (try and) open such files as pdf files, i.e., fall back to filename extension-based detection for application/octet-stream mimetyped files.

How To Open Application Octet Stream File

Is this possible to configure in the file associations kcm or in another way? An octet-stream is random binary data. You can assign it to eg. Okular, but that's 'wrong' since it's random binary data. What needs to happen is that whatever opens the file (kmail?) either prefers the suffix over the mimetype (ugghhh.) or (much better omits the (particular) mimetype, so that the system is forced to detect it.

How Do You Open Application/octet-stream

-> File a bug against whatever opens it. A shorthand 'solution' would likely be to assign octet-stream data to always be openened by 'kioclient[4 5] exec%U' (which redirects the opening and scratches the mimetype), but I've never tried that. => 'kcmshell[4 5] filetypes'.

Chrome has this awesome internal PDF viewer which makes the user experience really great. It triggers on web servers responding with the PDF content type (application/pdf). However, in reality a lot of web servers are simply returning application/octet-stream, with a file extension of '.pdf'. Those links trigger the 'warning' download which can be really confusing. I'm seeing this constantly, also on popular websites. I propose to handle files ending with '.pdf' of content-type 'application/octet-stream' the same way as files downloaded with 'application/pdf' - try to preview directly in Chrome with the internal PDF viewer, and on failure have the same fallback. Processing Cc: asanka@chromium.org Status: Untriaged Summary: Downloaded files of type application/octet-stream + file extension.pdf should be handled by internal PDF Viewer Asanka: Worth considering this as part of the plugin vs.

BufferredResourceHandler regularization work you're doing? I had assumed that most of the download when PDF viewer was wanted was due to content-disposition headers, but this is a plausible alternative user frustration pathway, and one that we might reasonably be able to fix. (We want to obey content-disposition.). Processing The other examples I had also all made the content-disposition header in addition. So let me re-phrase my wish then: On IE, the download is a dedicated dialog, it pops up in the foreground when done and gives the user an explicit 'open' action.

How To Open Octet-stream File Online

On Chrome-OS, the download is a subtle box at the bottom. It does not start downloading until the user agrees to a scary message.

Mime Application Octet Stream

And then there is no obvious way (at least not for me) to actually open that PDF in Chrome for preview. Is this a workflow which we could improve? I could imagine that for this specific case it would be valid to ask the user if he wants to download or view directly, and trust the content for immediate download given that this is a PDF (based on the file extension). Just an idea. Processing We've discussed overriding the Content-disposition header (you're not the only user who'd like that:-}) but concluded that we're not willing to arbitrarily override the website's explicit intention. It should be relatively easy to do with a Chrome extension.