Charles Lee wrote:
I don't see a problem with this proposal but I just wonder if this method is even used these days. It is a legacy method and I don't think anyone can rely on it to reliably detect any content type. I'm curious how you ran into this, was it a test or custom protocol handler that overrides getContentType and uses guessContentTypeFromStream as a fallback?Hi guys,With test case[1] below, you can see guessContent does not support UTF8/32 BOM.
-Alan.
