Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of pid@pidster.com designates
 74.125.82.173 as permitted sender)
Message-ID: <4E3FFC9E.3060800@pidster.com>
Date: Mon, 08 Aug 2011 16:11:26 +0100
From: Pid <pid@pidster.com>
Organization: Pidster Inc
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Tomcat 7.0.19 overrides the http status code on forward
References: 
 <CA+A8vzHDL1uLrdmGOxVu5C3pArm1L4wp7adw2hU8RXFu_=nHww@mail.gmail.com>
In-Reply-To: 
 <CA+A8vzHDL1uLrdmGOxVu5C3pArm1L4wp7adw2hU8RXFu_=nHww@mail.gmail.com>
OpenPGP: id=62590808
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 08/08/2011 15:07, Eugen Paraschiv wrote:
> I'm seeing some strange behavior with a RequestDispatcher forward in Tomcat.
> The the exact code doesn't generate the problem on Jetty, so it is probably
> related to the servlet implementation.
> 
> The problem is as follows: Spring does a forward on an existing
> request/response - at which point, the response has the http status code of
> 404; after the forward, the code is 500.
> 
> The actual logic happens in Spring (MVC), at: InternalResourceView -
> renderMergedOutputModel. The Spring code does mention that the forwarded
> resource is supposed to determine the content type itself, but nothing about
> the code being overridden as well.
> 
> I'm using Spring 3.0.5 on a JDK 6.0.26.
> 
> Any help on this is appreciated. Thanks.

Are there any errors in the logs?  Are the various log levels set
appropriately?

A 500 status often also produces a stack trace in the logs.  Does it in
this case?


p


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