On Thu, 14 Jun 2001, William F. Hammond wrote:
>>
>> Date: Fri, 4 May 2001 05:04:45 -0700 (Pacific Daylight Time)
>
> The specific issue in this sub-thread: What is the reason for a user
> agent's policy-level refusal to parse as xml, rather than as tag soup,
> an http object served as text/html upon finding an xml declaration at
> the body origin.
http://www.damowmow.com/mozilla/html-not-xml.html
>> In addition, there are several reasons why this is a bad idea in
>> the first place:
>> [...]
>> D. The Content-Type HTTP header is supposed to be the final word on
>> how to handle a data stream.
>
> The HTTP Content-Type header is the only means available to the user
> for deciding whether to give the HTTP object to an external application.
That too.
> "text/xml" is simply too general to be sensible for internal handling by
> unified http/html user agents.
I don't understand what that sentence means.
--
Ian Hickson )\ _. - ._.) fL
Invited Expert, CSS Working Group /. `- ' ( `--'
The views expressed in this message are strictly `- , ) - > ) \
personal and not those of Netscape or Mozilla. ________ (.' \) (.' -' ______
