Thanks, I will check that. For T3 it seems to be some more work (just checked the sources). For example you would have to make sure that an absolute URL is generated if you come from an unsecured page and so on...
If that's easier in T4 that would be one more reason for me to migrate. Cheers, Detlef -----Original Message----- From: Filip S. Adamsen [mailto:[EMAIL PROTECTED] Sent: 05 April 2006 14:51 To: Tapestry users Subject: Re: AW: https You can probably do that yourself if you really want to. I've been digging in the source code and as far as I can see, all you need is to overwrite the getScheme() method in your link component of choice to always return "https" if the page it refers to is considered protected by your application. You could get hold of the page and check for a "page-is-secure" meta-tag or something in that method and then act accordingly. A simpler approach, I guess, would be if your only protected page is some sort of login page... If that is the case, you could perhaps just make a LoginLink component? -Filip Detlef Schulze skrev: > Hmm. I wonder why there wasn't implemented something like a "secured" attribute on the page. Would be much simpler if the page knows that it should be secured an all links to it automagically use https. --------------------------------------------------------------------- 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]
