Actually the more I think abou this, it seemss feasible to implement
this feature in tapestry. As long as there is a default link renderer
code that every link uses, and can be configurable/changeable through
hivemind.
- add 'secure' meta-data to the page somehow
- change render cycle to throw an exception if trying to render a page
insecurely if it's marked secure.
- add configuration for application wide http/https port definition
- see if there is a default link renderer class that is pluggable
- change it to use the appropriate http/https depending target page
So it sounds feasible, but I don't think I will have the time to submit
this path any time soon.. sadly.
fernando
Korbinian Bachl wrote:
Dankeschön :)
sounds good so far - do we also have an easy way to let a page secure itself
?
e.g. a paramater in secret.page like "<component https_needed="1"/>" - and
whenever sb. accesses this page by http he gets an automatic redirect to
https ?
so we could get sure that a page is allways accessed via secure connection
and dont have to take care of unsecure
links ?
Regards,
Korbinian
-----Ursprüngliche Nachricht-----
Von: Filip S. Adamsen [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 5. April 2006 13:58
An: Tapestry users
Betreff: Re: AW: https
Natürlich. ; D
Check out the component reference for DirectLink,
ExternalLink, PageLink and ServiceLink - all these components
have a "scheme" parameter. Set it to "https" to enable https
- this will force the creation of an absolute URL if that
scheme does not match that of the current request.
...
---------------------------------------------------------------------
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]
