Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 86247 invoked from network); 4 Feb 2004 21:24:28 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Feb 2004 21:24:28 -0000 Received: (qmail 67674 invoked by uid 500); 4 Feb 2004 21:23:33 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 67644 invoked by uid 500); 4 Feb 2004 21:23:33 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 67602 invoked from network); 4 Feb 2004 21:23:32 -0000 Received: from unknown (HELO minnie.omroep.nl) (145.58.30.4) by daedalus.apache.org with SMTP; 4 Feb 2004 21:23:32 -0000 Received: from tron.omroep.nl (tron.omroep.nl [145.58.31.20]) by minnie.omroep.nl (Postfix) with ESMTP id 1BBC81CF20EB for ; Wed, 4 Feb 2004 22:23:38 +0100 (CET) Received: from michiel.omroep.nl (michiel.omroep.nl [145.58.67.10]) by tron.omroep.nl (Postfix) with ESMTP id 11A1A10056BD for ; Wed, 4 Feb 2004 22:23:38 +0100 (CET) Received: from michiel by michiel.omroep.nl with local (Exim 3.35 #1 (Debian)) id 1AoUUj-00037Z-00 for ; Wed, 04 Feb 2004 22:23:37 +0100 Date: Wed, 4 Feb 2004 22:23:37 +0100 From: Michiel Meeuwissen To: Tomcat Users List Subject: Re: charset problem Message-ID: <20040204212337.GC28025@michiel.omroep.nl> Reply-To: Michiel Meeuwissen Mail-Followup-To: Michiel Meeuwissen , Tomcat Users List References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Publieke Omroep []() User-Agent: Mutt/1.5.4i Sender: Michiel Meeuwissen X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Sander de Boer wrote: > 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"); %> > <%@page language="java" contentType="audio/x-pn-realaudio" %> > > 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@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org