Guten Tag Sven Meier, am Sonntag, 6. März 2016 um 22:08 schrieben Sie: > I wouldn't expect Wicket to generate an empty location header. Can you > reproduce this problem in a Wicket quickstart?
You are right, I forgot to mention it: During debugging I already noticed that Wicket is in fact rendering "./" instead of an empty string using UrlRenderer.renderRelativeUrl, but I thought this might get changed later to an empty string for some reason. I created a quickstart and "sadly" this worked as expected, the client is getting the following header: > Location:http://localhost:8081/org.example.frontend/ But in the debugger the processing looks identical to my problem, the quickstart renders "./" as well. The only difference seems to be that in my case the browser isn't getting a properly resolved URL anymore, but and empty string or such, while that's not the case with the quickstart. My servlet container with the problem is Tomcat 7, while the quickstart uses embedded Jetty? I guess I'll need to focus on that for now and find a difference. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
