Mailing List Archive

Well, I've corrected the typo, but I don't know the answers to his
questions. For example, could some explain to me what
text/x-server-parsed-html3 is for???

More tales from ancient days... it exists so that content negotiation
can distinguish between SSI-bearing HTML2 and SSI-bearing HTML3 (so that
only clients which accept HTML3 get the latter if the server has a choice).

rst

Forwarded message:
> Subject: Multiviews: errors in documentation
> From: Michiel Boland <boland@sci.kun.nl>
>
> In your documentation on content negotiation
> (http://www.apache.org/docs/content-negotiation.html) you write
>
> Apache also supports a new pseudo-MIME type,
> text/x-server-processed-html3, which is treated as
> text/html;level=3 for purposes of content negotiation, and as
> server-side-included HTML elsewhere.
>
> This is wrong; the MIME type is actually
> text/x-server-parsed-html3
> ^^^^^^
>
> Also, if one wants Multiviews *and* HTML3 one has to turn on the
> html parsing mechanism, e.g.:
>
> <Directory /this/dir/has/multiviews/enabled>
> Options Multiviews IncludesNoEXEC
> </Directory>
>
> Am I correct in thinking that Apache actually *parses* each
> html3 file??? (whereas it would not parse an ordinary html file)
> This seems rather a waste to me (this may be fixed in v0.8.x -
> however I can't get this to run yet with my own patches, so im
> sticking to 0.6.4b for the moment)

Well, I've corrected the typo, but I don't know the answers to his
questions. For example, could some explain to me what
text/x-server-parsed-html3 is for???

David.

text/x-server-parsed-html; level=3 doesn't work. Therefore,
text/x-server-parsed-html3 is preferred.

rst

> Well, I've corrected the typo, but I don't know the answers to his
> questions. For example, could some explain to me what
> text/x-server-parsed-html3 is for???
>
>More tales from ancient days... it exists so that content negotiation
>can distinguish between SSI-bearing HTML2 and SSI-bearing HTML3 (so that
>only clients which accept HTML3 get the latter if the server has a choice).

Hmm. Is it useful anymore? Or is text/x-server-parsed-html; level=3
to be preferred?

A document with mime type text/x-server-parsed-html3 is returned to the
client with type simply text/html -- is this correct, or should it be
text/html3 or text/html; level=3?

David.

>text/x-server-parsed-html; level=3 doesn't work. Therefore,
>text/x-server-parsed-html3 is preferred.

But why does text/x-server-parsed-html3 come back as text/html ?

David.