Thanks for responding. I am still unsure about a few things.
>
> a) that session tracking is functional on the particular
> combination of
> browser/container/etc without entering an infinite redirect loop,
The only reason it would enter an infinite loop though is because Turbine sends it
into one!? i.e. If session tracking is not
working then turbine sends it into a loop, but catches this and throws an infinite
redirect error. Do I really need this if I am
working with a standard app server like Tomcat?
> b) that no redirect specifies the same URL as the request
Actually turbine doesn't catch this if it is done by the application, only if it
happens on the initial (new session) request.
Has anybody else removed this code and then had problems? What browsers give problems?
I would love someone to convince me that it
is necessary, but I just can't see how.
Gareth
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
