[WICKET-2629] HttpsRequestCycleProcessor causes HttpSession to be created

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.4.4
• Fix Version/s: 1.4.6
• Assignee: Igor Vaynberg
• Reporter: Damien Hollis
• Created: 21/Dec/09 02:30
• Updated: 30/Aug/10 13:02
• Resolved: 21/Dec/09 05:06

Description

The HttpsRequestCycleProcessor has the following code:

public IRequestTarget resolve(RequestCycle rc, RequestParameters rp)

{ // we need to persist the session before a redirect to https so the session lasts across // both http and https calls. Session.get().bind(); IRequestTarget target = super.resolve(rc, rp); return checkSecure(target); }

The Session.get().bind() causes an HttpSession to be created even if the target page is stateless. In our application all our pages are https and our login page is stateless. Because the session is created anyway, we are now exposed to a DoS attack.

I don't really see why a HttpSession needs to be forced here. If the page is stateful, then a session will be created anyway. If the current page is stateless but the user had already navigated stateful pages, then a session will be present again. Is there a scenario where it is important to for the session creation? Can a mechanism be provided that will disable this behaviour?

Issue Links

• is cloned by: WICKET-2903 CLONE -HttpsRequestCycleProcessor causes HttpSession to be created