Server attributes in Http connector

[Wu Haibao-a15761 <a1...@motorola.com>]

 
Hi,
 
    I got a problem with Tomcat that it enforces "charset=ISO-8859-1" to
the Content-Type header in the response. It's very much like the problem
as described in this page:
http://groups.google.com/group/microsoft.public.windows.inetexplorer.ie6
.browser/browse_thread/thread/dda4148694bf9179/6ebf14176d967e16?lnk=st&q
=charset%3DISO-8859-1+%22content+type+header%22+tomcat&rnum=4&hl=en#6ebf
14176d967e16
<http://groups.google.com/group/microsoft.public.windows.inetexplorer.ie
6.browser/browse_thread/thread/dda4148694bf9179/6ebf14176d967e16?lnk=st&
q=charset%3DISO-8859-1+%22content+type+header%22+tomcat&rnum=4&hl=en#6eb
f14176d967e16> 
        And I just found there's a "server" attribute in Tomcat 5.5.16,
but the description is too simple to be helpful in use:

server	 The Server header for the http response. Unless your paranoid,
you won't need this feature. 

        Does anyone know about this attribute?  And I am not sure if
this is the way I may change to avoid the "charset=ISO-8859-1" in
response.

        Thanks.

Regards,

Wu Haibao  

==============================
[X]General Business Information 
[]Motorola Internal Use Only 
[]Motorola Confidential Proprietary 
 

Re: Server attributes in Http connector

[Tim Funk <fu...@joedog.org>]

The Server attribute is for setting the server name on the response. For 
example, you can have tomcat server back:

200 Ok
Server: More Cowbell/1.0
...

As for the "charset=ISO-8859-1" - See the tomcat-user archives and bugzilla 
about this. I can't recall the outcome of the various resolutions for this vs 
different tomcat versions. But it has been discussed many times.

The root cause is the way JSP's are initialized and spec'd. It was expected 
that JSP's serve text. So a charset is always needed. Due to edge cases, this 
isn't always the case. So various bugs/interpretations arise.

-Tim

Wu Haibao-a15761 wrote:
>  
> Hi,
>  
>     I got a problem with Tomcat that it enforces "charset=ISO-8859-1" to
> the Content-Type header in the response. It's very much like the problem
> as described in this page:
> http://groups.google.com/group/microsoft.public.windows.inetexplorer.ie6
> .browser/browse_thread/thread/dda4148694bf9179/6ebf14176d967e16?lnk=st&q
> =charset%3DISO-8859-1+%22content+type+header%22+tomcat&rnum=4&hl=en#6ebf
> 14176d967e16
> <http://groups.google.com/group/microsoft.public.windows.inetexplorer.ie
> 6.browser/browse_thread/thread/dda4148694bf9179/6ebf14176d967e16?lnk=st&
> q=charset%3DISO-8859-1+%22content+type+header%22+tomcat&rnum=4&hl=en#6eb
> f14176d967e16> 
>         And I just found there's a "server" attribute in Tomcat 5.5.16,
> but the description is too simple to be helpful in use:
> 
> server	 The Server header for the http response. Unless your paranoid,
> you won't need this feature. 
> 
>         Does anyone know about this attribute?  And I am not sure if
> this is the way I may change to avoid the "charset=ISO-8859-1" in
> response.
> 

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