|
|
Hi Sam,
> Well, you've always got access to the Request object, which
> would allow you to detect in a BasePage class whether the
> incoming request was secure or not.
of course we have it - but based on that we wouldnt need tapestry as we
always could do a manual way around ;)
but seriously: i also use T4 - what do you mean with Tap4 has it included ?
- shame on me but i havent found it yet...
Regards,
Korbinian
> -----Ursprüngliche Nachricht-----
> Von: sgendler@xxxxxxxxx [mailto:sgendler@xxxxxxxxx] Im
> Auftrag von Sam Gendler
> Gesendet: Mittwoch, 5. April 2006 12:36
> An: Tapestry users
> Betreff: Re: https
>
> Well, you've always got access to the Request object, which
> would allow you to detect in a BasePage class whether the
> incoming request was secure or not. The pageValidate()
> method of your base page (or the tap3 equivalent, I suppose)
> could handle redirecting before the page even renders. In
> the worst case, run two instances of your application, one
> secure and one not, do manual detection in the your base page
> class, and with a tiny bit of cookie trickery, you could
> maintain enough state in the client to recognize the user in
> either application in a reasonably secure manner. Of course,
> shopping carts and the like would have to persist in some
> kind of shared storage, but it certainly isnt unworkable.
> That said, I'm a Tap4 user, so this isn't, apparently, an
> issue for me. In my case, I'm building customer facing
> enterprise apps that pass lots of sensitive data back and
> forth, so the entire app behind an SSL capable load balancing
> switch is pretty much the norm.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-user-help@xxxxxxxxxxxxxxxxxx
|
|