Re: signOut and port

2012-01-10 Thread brettTi
Yea, I was already doing all that.  The issue was the :8443 in the url, which
is accurate but bothersome since we are trying to hide that with iptables.

Fixed it by throwing a RedirectToUrlException with the port number left out
of the url.

View this message in context:
Sent from the Users forum mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

Re: signOut and port

2012-01-03 Thread Jeremy Thomerson
On Mon, Jan 2, 2012 at 5:38 PM, brettTi wrote:

 We're running a wicket app on jetty and having an issue with signout. The
 runs on port 8443 and we have iptables redirecting from port 443.  This
 us go to https://ourap.lab without port numbers and without having the web
 app run as root.

 Everything is great until we do signout.  We have a LogoutPage that does


 Works fine, we get sent to the Login page.  Only problem is that the url
 the :8443 port number in it.  For some reason, this is the end of the world
 for our users.

 Any ideas?  Thanks

Maybe a combination of these two things:

First, do the iptables packet redirection [1] - sounds like you have this
Then, tell Wicket what port to send redirects to [2] - sounds like this may
fix your problem.


Jeremy Thomerson
*Need a CMS for Wicket?  Use Brix!*