Sander de Boer <sander@(protected):
> Since I have upgraded to tomcat 4.1.29(from 4.1.27) tomcat sets a default
> charset(ISO-8859-1)
>
> I set:
> <% response.setContentType("audio/x-pn-realaudio"); %>
> <%@(protected)" %>
>
> Tomcat gives:
> Content-Type: audio/x-pn-realaudio;charset=ISO-8859-1
>
> I have also tried tomcat 4.1.30(alpha) but with the same problem.
>
> So, what is the problem?


Of course it should not really be a problem, because specifying the correct
charset when you are specifying the content type should be rather
straight-forward.

But I gather that you want it _not_ to specify the charset because a
certain program (real-player) completely chokes in that?

To work around this kind of troubles I agree that it should be possible to
explicitely set the content type while explicitily _not_ setting the
charset.

Why is that not possible?

Michiel



--
Michiel Meeuwissen
Mediapark C101 Hilversum
+31 (0)35 6772979
nl_NL eo_XX en_US
mihxil'
[] ()

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)