Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <4107DB3E.20306@apache.org>
Date: Wed, 28 Jul 2004 18:58:38 +0200
From: Remy Maucherat <remm@apache.org>
User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707)
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: cvs commit:
 jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote
 Response.java
References: <20040728004317.61647.qmail@minotaur.apache.org>
 <019d01c4743e$cf70b140$6c37a8c0@bbarkerxp> <4107D8F7.3010105@sun.com>
In-Reply-To: <4107D8F7.3010105@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Jan Luehe wrote:

> Bill,
>
>> then I'd suggest simply
>> doing:
>>    setCharacterEncoding(getCharacterEncoding());
>> in Response.getWriter (since the spec only requires that we identify the
>> charset when using a Writer, and we don't really know what it is when 
>> using
>> OutputStream).
>
>
> The problem with this is that if you call getWriter() (with your 
> proposed fix) followed by getContentType(), the returned content type
> will include a charset, which is against the spec of getContentType():
>
>   * If no character encoding has been specified, the
>   * charset parameter is omitted.
>
> This is why we need to append the default charset to the value of the
> Content-Type header, if no char encoding has been specified.

This is not acceptable, and is not an option, so you shouldn't be using 
"we need", because we won't ;)
The right solution is IMO to point out the issues to the specification 
people.

R�my


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org