Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <3E93FFA4.2010508@joedog.org>
Date: Wed, 09 Apr 2003 07:10:28 -0400
From: Tim Funk <funkman@joedog.org>
Organization: Human being
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3b) Gecko/20030210
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Different Content Type returned by Tomcat 4.1 and Tomcat 4.0.
 Please Help!
References: <F99hiDlw3AqdqlvhmZq00006551@hotmail.com>
In-Reply-To: <F99hiDlw3AqdqlvhmZq00006551@hotmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

For the invoker servlet being commented out by default:
http://tomcatfaq.sourceforge.net/miscellaneous.html

-Tim

Sergei Ostavnenko wrote:
> Yoav,
> Thank you very much for your comment.
> The idea with filter sounds like a good option.
> 
> Although, I still have a feeling that certain Tomcat configuration 
> options should be available in order to make it handle the Content Type 
> in the same way as Tomcat 4.0 does.  Any ideas on that?
> 
> As to the invoker... I do have the invoker mapping uncommented (I'm not 
> sure why it's commented in latest versions though), but for particular 
> application that I have problem with, it doesn't even matter: all the 
> servlets are mapped in it's own web.xml.
> Anyway I did try with the invoker mapping commented and uncommented - 
> same problem as far as Content Type in header is concerned.
> 
> Thanks a lot,
> 
> Sergei Ostavnenko
> 
> 


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