Kevin Koltzau wrote:
IE overrides MIME types for more then just ambiguous types, to quote one test mentioned in the appendix
"If the server-provided MIME type is either known or ambiguous, the buffer is scanned
in an attempt to verify
or obtain a MIME type from the actual content. If a positive
IE overrides MIME types for more then just ambiguous types, to quote one test
mentioned in the appendix
"If the server-provided MIME type is either known or ambiguous, the buffer is scanned
in an attempt to verify
or obtain a MIME type from the actual content. If a positive match is found (one o
Kevin, you said:
IMHO we should really keep the list that is checked to
a minimum (being the list Windows checks)
as this code is basically doing "If a web server
reports a MIME type in this list, ignore it and
make our own guess" which is totally wrong
standards-wise and a major cause of many
prob
I had thought of that, the major reason I implemented it the way I did was based off of
the MSDN document mentioned, which states Windows has a very select list of
types that it checks.
IMHO we should really keep the list that is checked to a minimum (being the list
Windows checks)
as this code i
On Thu, 18 Mar 2004 11:38:58 -0500, Kevin Koltzau wrote:
> Here is an implementation of FindMimeFromData, based off of MSDN
> http://msdn.microsoft.com/workshop/networking/moniker/overview/appendix_a.asp
Hmm, I'm not sure we should maintain this ourselves. A better approach
might be to use the fre
Here is an implementation of FindMimeFromData, based off of MSDN
http://msdn.microsoft.com/workshop/networking/moniker/overview/appendix_a.asp
There is lots of debate on the 'net regarding this "feature" in IE, most of it
suggesting
this is a bad idea..
One possible change that would work more "
