Jean-Michel Leon wrote:

>
> this deliberate behavior in tomcat is wrong (i.e. it's a bug), because
> the servlet spec does not specify that servlets should override the
> programmer's contnet-type wth its own defaults.
>

In other words, you would like the following sequence of events:

    <%
        response.setHeader("Content-Type", "foo/bar");
        response.setContentType("x-application/my-content-type");
    %>

to result in a content type of "foo/bar", despite the fact that the programmer
explicitly sets it?  Seems to me you could make a case that this is a bug, just as
strongly as the argument you are making.

I remind you again -- in the case where the servlet spec is not speciific (it is silent
on the topic you are raising regarding content type; not quite so silent on content
length -- see the 2.2 API docs), i.e. it is an interpretation issue, the reference
implementation defines correct behavior.  And guess what the reference implementation
here is?

>
> jm.
>

Craig

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.html

Reply via email to