[Yanel-dev] [Bug 4787] apply "patchMimeType" method from YanelServlet everywhere application/xhtml+xml is being set

[bugzilla at wyona.com]

http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=4787


guillaume.deflache at wyona.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|apply "patchContentType"    |apply "patchMimeType" method
                   |method everywhere           |from YanelServlet everywhere
                   |application/xhtml+xml is    |application/xhtml+xml is
                   |being set                   |being set




------- Comment #3 from guillaume.deflache at wyona.com  2009-02-02 10:08 -------
Also for a practical note from W3C on among others how to handle
application/xhtml+xml see
http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116/

As summarized from http://www.cafeconleche.org/oldnews/news2009February1.html
here is what we should do:
>        1.  If the Accept header explicitly contains application/xhtml+xml (with either no "q" parameter or a positive "q" value) deliver the document using that media type.
>        2. If the Accept header explicitly contains text/html (with either no "q" parameter or a positive "q" value) deliver the document using that media type.
>        3. If the accept header contains "*/*" (a convention some user agents use to indicate that they will accept anything), deliver the document using text/html.
> 
>     In other words, requestors that advertise they support XHTML family documents will receive the document in the XHTML media type, and all other requestors that (at least claim to) support HTML or "everything" will receive the document using the HTML media type. Dealing with user agents that satisfy none of these criteria is outside the scope of this document.


-- 
Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.