A.M. Kuchling wrote:
> On Fri, Sep 10, 2004 at 02:49:45PM -0400, Kirill Lapshin wrote:
>
> Is the CSS file being served as text/css?  To do this, put
> request.response.set_content_type('text/css') in the handler for your
> CSS file (if it's served via Quixote).

You are right. That was a culprit. Changing content type to text/css
fixed the problem.

> Shouldn't it be application/xhtml+xml?  See
> http://www.xml.com/pub/a/2003/03/19/dive-into-xml.html.  You can set
> the content type by calling request.response.set_content_type(), as
> above.

Yep, you are correct and I am wrong. Quoting W3C:

The 'application/xhtml+xml' media type [RFC3236] is the media type for
XHTML Family document types

'application/xhtml+xml' SHOULD be used for serving XHTML documents to
XHTML user agents.

Any XHTML Family document MAY be served as 'application/xml'.

Any XHTML Family document MAY be served as 'text/xml'.

The 'text/html' media type [RFC2854] is primarily for HTML, not for
XHTML. In general, this media type is NOT suitable for XHTML. However,
as [RFC2854] says, [XHTML1] defines a profile of use of XHTML which is
compatible with HTML 4.01 and which may also be labeled as text/html.

Since I am developing intranet app, I have a luxury of not worrying
about obsolete user agents, so I guess I'll go down
application/xhtml+xml route.


Next question -- is there a way to define default content type for
application? I can certainly set it in every resource, but setting it
once and for all would be much cleaner. Not a big deal though, I have a
header() template, which can be modified to take request and set content
  type.

Thanks for your help.

--Kirill