On Mon, 19 Feb 2001 15:17:56 -0500, Clarence Verge wrote:
> Glenn McCorkle wrote:
>> On Sun, 18 Feb 2001 20:14:29 -0500, Clarence Verge wrote:
>> <snip>
>> > Anyway, I would prefer to keep the correct extension and operate on that
>> > basis instead of mimetype if possible. ;-)
>> Ahhhh, now you've touched on the "permanant fix".
>> If we disregard "content-type", "content-encoding" and file extension
>> but instead look inside the file itself to see what needs to be done. :)
> No, I wouldn't recommend going to THAT extreme.
> What I would like to see is pretty simple.<g>
> If the extension and content-type agree, go with it.
> If they disagree, use the extension.
> You can see that the above is satisfied if you simply go with the extension.
> I'd like atleast an option to allow the file extension to have priority over
> content-type/mimetype.
Your idea would work to cure the problem of
"incorrect content-type/file_extension"
However, I call looking inside the file itself "perfect" because it
would cure "incorrect content-type/file_extension" *and*
"incorrect file_extension/actual_file_content"
I have just uploaded 4 examples that can only be cured by looking inside
the file itself.
http://www.angelfire.com/id/glenndoom/t-not-h.htm
http://www.angelfire.com/id/glenndoom/h-not-t.txt
http://www.angelfire.com/id/glenndoom/j-not-g.gif
http://www.angelfire.com/id/glenndoom/g-not-j.jpg
--
Glenn
http://arachne.cz/
http://freedos-32.sourceforge.net/
http://www.delorie.com/listserv/mime/
http://www.angelfire.com/id/glenndoom/download.htm
