On 02/18/2015 10:20 AM, Ben Titmarsh wrote:
Hey Guys,
I've just got my web server set up for SSL and it's working, but am
experiencing some odd behaviour from Tapestry. I've added the @Secure
annotation to one of my pages but by default the link is generated thus:
https://[DOMAIN]:80/login
I tried adding:
configuration.add(SymbolConstants.HOSTPORT_SECURE, "443");
The link is now generated correctly like this (without a port):
https://[DOMAIN]/login
However when I hit that link, it gets caught in an infinite 302 redirect loop.
I can quite happily hit any page without the @Secure annotation over https and
it loads fine.
Any pointers?
Thanks,
Ben.
I think you might need configuration.add(MetaDataConstants.SECURE_PAGE,
Boolean.TRUE.toString());
I know I have to add that to stop it from putting the port in. We're
doing TLS to HTTPD, then AJP to Tomcat with the connector set to https
for the scheme and secure set to true. That particular thing only seems
to kick in when production mode is true.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
