<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: HttpServletRequestWrapper, Tomcat and forwards</title>
	<atom:link href="http://brian.pontarelli.com/2008/01/16/httpservletrequestwrapper-tomcat-and-forwards/feed/" rel="self" type="application/rss+xml" />
	<link>http://brian.pontarelli.com/2008/01/16/httpservletrequestwrapper-tomcat-and-forwards/</link>
	<description>Brian Pontarelli</description>
	<pubDate>Thu, 08 Jan 2009 11:48:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Brian Pontarelli</title>
		<link>http://brian.pontarelli.com/2008/01/16/httpservletrequestwrapper-tomcat-and-forwards/#comment-8932</link>
		<dc:creator>Brian Pontarelli</dc:creator>
		<pubDate>Thu, 21 Feb 2008 15:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://brian.pontarelli.com/2008/01/16/httpservletrequestwrapper-tomcat-and-forwards/#comment-8932</guid>
		<description>It was pretty simple. I just wrapped the request so that the request URI was something different. This was done in a filter. The request got passed down to struts and struts pulled out the new URI correctly and invoked the action. Once the action finished Struts tried to forward the request to the JSP and this is where it failed. The container was unable to perform the forward because the HttpServletRequest that was being passed to the request dispatcher had a different request URI and was a wrapper. Tomcat doesn't like that and was throwing some strange exceptions back.</description>
		<content:encoded><![CDATA[<p>It was pretty simple. I just wrapped the request so that the request URI was something different. This was done in a filter. The request got passed down to struts and struts pulled out the new URI correctly and invoked the action. Once the action finished Struts tried to forward the request to the JSP and this is where it failed. The container was unable to perform the forward because the HttpServletRequest that was being passed to the request dispatcher had a different request URI and was a wrapper. Tomcat doesn&#8217;t like that and was throwing some strange exceptions back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://brian.pontarelli.com/2008/01/16/httpservletrequestwrapper-tomcat-and-forwards/#comment-8819</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 19 Feb 2008 21:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://brian.pontarelli.com/2008/01/16/httpservletrequestwrapper-tomcat-and-forwards/#comment-8819</guid>
		<description>How did you discover that tomcat failed on forwards when the request had been wrapped? I can't find any information online and the workaround you are using will not work for me since I need to have the wrapped request for the resource being forwarded to.</description>
		<content:encoded><![CDATA[<p>How did you discover that tomcat failed on forwards when the request had been wrapped? I can&#8217;t find any information online and the workaround you are using will not work for me since I need to have the wrapped request for the resource being forwarded to.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
