Bill Barker wrote On 02/02/06 11:32,:
>
>
>
>>-----Original Message-----
>>From: Remy Maucherat [mailto:[EMAIL PROTECTED]
>>Sent: Thursday, February 02, 2006 4:02 AM
>>To: Tomcat Developers List
>>Subject: Re: svn commit: r371765 -
>>/tomcat/container/tc5.5.x/catalina/src/share/org/apache/catali
>>na/connector/Response.java
>>
>>Bill Barker wrote:
>>
>>>Yes, RFC 2616 does specify iso-latin-1 as the default for
>>
>>HTTP/1.1 clients.
>>
>>>However, section 3.4.1 is also relevant for HTTP/1.0
>>
>>clients (like, say, the
>>
>>>TCK :). In any case, it doesn't matter since section 5.4
>>
>>of the servlet
>>
>>>spec says "must". Complaints go to the expert group; here
>>
>>we just develop
>>
>>>Tomcat.
>>
>>Ok, so I asked the expert group, and many people interpret the
>>specification as I do (and is logical to do): if the
>>application uses a
>>writer, and never specifies the charset in any way, the
>>container has no
>>business rewriting the content-type header to include
>>";charset=ISO-8859-1".
>>
>
>
> Then they should make the language in the spec clearer ;-).
>
> If I'm misunderstanding the spec, then I don't have a valid reason for my
> veto. Consider the veto withdrawn.
I don't think you are misunderstanding the spec.
See the following javadocs snippets from ServletResponse:
public String getCharacterEncoding():
* If no character encoding
* has been specified, <code>ISO-8859-1</code> is returned.
public PrintWriter getWriter() throws IOException:
* If the response's character encoding has not been
* specified as described in <code>getCharacterEncoding</code>
* (i.e., the method just returns the default value
* <code>ISO-8859-1</code>), <code>getWriter</code>
* updates it to <code>ISO-8859-1</code>.
public void setCharacterEncoding(String charset):
* <p>Containers *must* communicate the character encoding used for
* the servlet response's writer to the client if the protocol
* provides a way for doing so. In the case of HTTP, the character
* encoding is communicated as part of the <code>Content-Type</code>
* header for text media types.
Jan
>
>
>>Rémy
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
>
>
> This message is intended only for the use of the person(s) listed above as
> the intended recipient(s), and may contain information that is PRIVILEGED and
> CONFIDENTIAL. If you are not an intended recipient, you may not read, copy,
> or distribute this message or any attachment. If you received this
> communication in error, please notify us immediately by e-mail and then
> delete all copies of this message and any attachments.
>
> In addition you should be aware that ordinary (unencrypted) e-mail sent
> through the Internet is not secure. Do not send confidential or sensitive
> information, such as social security numbers, account numbers, personal
> identification numbers and passwords, to us via ordinary (unencrypted) e-mail.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
