Thanks! I'm gonna have a look at those frameworks. I've just noticed the
"scheme" parameter on the form component:
http://tapestry.apache.org/tapestry4/tapestry/ComponentReference/Form.html
May be this may help as well under some circumstances, but I think the
filter approach will be a lot more helpful to secure different sections
of the application globally.
Thanks again for the help!
mika
Kalle Korhonen wrote:
Depends on the security framework you use, not really a Tapestry function.
Acegi makes it configurable and also AppFuse has a configurable filter for
it.
Kalle
On 9/4/06, Mika Tammilehto <[EMAIL PROTECTED]> wrote:
Hi!
Is there a "best-practice"-approach in Tapestry (4.0) to switch from
HTTP to HTTPS and back again, depending on the page?
We could write a servlet filter to switch to secure connection when
necessary but maybe there's a simple way to do it in Tapestry... any
idea?
Thanks a lot in advance!
Cheers,
mika
---------------------------------------------------------------------
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]
