Can't you use your web server's redirect function to take care of
this? On tomcat, for example, you specify:
<security-constraint>
<web-resource-collection>
<web-resource-name>Corinna</web-resource-name>
<url-pattern>/foo/bar/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
And then any url that starts with /foo/bar automatically goes to
https.
In my experience that's a lot cleaner (not to mention a lot easier)
than having your application try to sort out what should, and should not, go
out over https.
The only issue with Tapestry is that it's sometimes awkward to use
pattern matching with tapestry urls because they look so funky, but since
you're using external links that shouldn't be a problem.
--- Pat
> -----Original Message-----
> From: Glen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 03, 2006 10:16 AM
> To: tapestry-user@jakarta.apache.org
> Subject: changing an external link to use https
>
> For reasons out of my control I have a webapp that runs on port 8081 and
> has an SSL proxy/accelerator in front of it on port 443.
>
> What I am seeing is that when the request comes in from the proxy if the
> url in the browser is https://myserver.com:443... The url for my
> external link and redirects is http://myserver.com:443...
>
> Is there anyway to fix this? I have heard mentione before a url
> listener/rewriter. Would this work? Would it work for external link,
> direct link, and redirects?
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
