RequestDispatcherMimic forward/include replaces an existing HttpSession if it is "new"
Reported by Michael Kaufman on ObMimic · 30/06/2014 20:30:36
- Assigned to:
- Michael Kaufman
- Servlet API implementation
- Fixed in version:
- Java SE version:
If an HttpServletRequestMimic has a current HttpSession that is newly-created during the request’s processing (rather than being an existing HttpSession “joined” via the request’s session-tracking properties), calls to RequestDispatcherMimic “forward” or “include” result in the existing HttpSession being removed and replaced with a new HttpSession instance (albeit with the same session ID).
Thus after the “forward” or “include”, there is still an HttpSession and it has the same session ID as before but any attributes that were stored in it appear to have been cleared.
No attachment has been uploaded, yet.