[WICKET-4776] Problems with switching between HTTP/HTTPS

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.6, 1.5.7, 1.5.8, 6.0.0
• Fix Version/s: 6.2.0, 1.5.9
• Component/s: wicket
• Assignee: Sven Meier
• Reporter: Matthias Remy
• Created: 21/Sep/12 09:29
• Updated: 01/Oct/12 08:24
• Resolved: 01/Oct/12 08:24

Description

Testcase, two Pages (A and B)
Page A: two Links to Page B
-Link1: setResponsePage(PageB.class);
-Link2: setResponsePage(new PageB());

Page B: "@RequireHttps", two Links to Page A
-Link1: setResponsePage(PageA.class);
-Link2: setResponsePage(new PageA());

Clicking link1 behaves equal in every Version i tested. No Problems switching between Page A and B and HTTP/HTTPS-change is working like expected (except status 404 at Page B in 1.5.6).

Clicking link2 behaves very strange.
Link2-Behavior in different Versions:
1.5.4/5 (and i guess older): Everything working correct like Link1.
1.5.6: Status 404 on Both Links at Page B

1.5.7/8/6.0.0:
If i go from Page A to B, Page B isn't called with https.
Now I'm on Page B an go to Page A, A is called WITH https?!?!
Then, moving one more to B, https is switching again to http.

This is very confusing, Page A without requireHttps is called with https, Page B with requireHttps is called without https?!
This leads in most cases on my website to a "Page B" where Links/Buttons/etc aren't working anymore.

Issue Links

• is broken by: WICKET-4561 Wicket 1.5.6 duplicates segments in absolute URLs