Re: Dealing with encodings and file: URIs

It also might be nice if an HTTP server reporting "text/plain" (no 
character set) didn't override the client specification of "text/plain; 
windows/1252", since they don't in fact conflict: the server is simply 
providing less information.

-Mike

Norman Walsh wrote:
> "Toman_Vojtech@emc.com" <Toman_Vojtech@emc.com> writes:
>   
>> Um. What kind of filesystem are you using that tells you the content
>> type?
>>     
>
> I suppose, on reflection, that that gives me justification to ignore
> the content type reported by java.net.URL. There really isn't a server
> involved.
>
>                                         Be seeing you,
>                                           norm
>
>