Chrome is not open source. From the behavior, I don't believe MIME is
involved. Remove the file type extension (e.g. jpg or pdf) and specify the file
in the chrome address bar. I think chrome looks for eye catchers in file data
to determine how to open the file.
This does not rule out some of the concepts involved with mime (e.g. use PHP or
some other SSI to include a header with the file content information). I don't
know if Chrome ignores or honors this information.
Jon.
On Tuesday, August 6, 2019, 11:03:02 AM PDT, Paul Gilmartin
<[email protected]> wrote:
On Tue, 6 Aug 2019 04:55:50 +0000, Jon Perryman wrote:
> ...
>For security reasons, Chrome does not support Windows file extensions. This is
>a huge security exposure with other browsers (e.g. MS Word autorun script).
>There are very few extensions that chrome supports (e.g. PDF) and they use
>very specific low risk programs (not acrobat) to reduce the risk. It's very
>unlikely they will support file extensions. ...
>
Does it support and even require (a subset of) MIME (RFC 1521) Content-types?
What does it do if a (standard) Content-type differs from the (customary) file
extension?
What about the somewhat deprecated Flash?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
