[
https://jira.jboss.org/jira/browse/JBSEAM-3875?page=com.atlassian.jira.pl...
]
Stephen Friedrich commented on JBSEAM-3875:
-------------------------------------------
Hm, the RewritingResponse extends HttpServletResponseWrapper.
I don't know how (or even if) url rewriting is working in a portlet context.
RewritingResponse gets passed HttpServletRequest and HttpServletResponse in its
constructor and is already storing the request in a field anyway, so the same should
probably be done for the response (avoiding the cast and call to super).
Seam's Rewrite filter breaks URL-session-id-rewriting
-----------------------------------------------------
Key: JBSEAM-3875
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3875
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Reporter: Stephen Friedrich
If Seam's rewrite filter is enabled, the session id is never added as a parameter to
URLs.
That should happen when one of the HttpServletResponse.encode...() methods is called and
no session cookie is found.
However the rewrite filter adds a response wrapper that delegates all encode methods to a
method that only (possibly) rewrites the URL according to defined rewrite-rules, but never
actually let's the servlet container encode the url.
Fix: In org.jboss.seam.web.RewritingResponse.encodeURL(String) add this line:
result = ((HttpServletResponse) getResponse()).encodeURL(result);
before returning the result.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira