In message <[EMAIL PROTECTED]>,
Heiko Braun <[EMAIL PROTECTED]> writes
>the thing is that i get an "Infinite redirect detected..."
>error, from within my turbine app. i can locate the source
>which produces the error, but unfortunatly i cant reproduce
>it. does anyone know if their is a certain client that has problems
>interpreting turbine/tomcat produced header information?
>
>maybe someone can explain the following lines to me:
>
>xxx.xx.xxx.xx - - [14/Oct/2001:21:27:34 1000] "HEAD
>/mag/servlet/mag HTTP/1.1" 302 234
>xxx.xx.xxx.xx - - [14/Oct/2001:21:27:34 1000] "HEAD
>/mag/servlet/mag/redirected/true HTTP/1.1" 200 -
>xxx.xx.xxx.xx - - [14/Oct/2001:21:27:35 1000] "GET
>/mag/servlet/mag/redirected/true HTTP/1.1" 200 2484
Someone is using either a browser or an intermediate agent (eg proxy)
that is breaking session tracking (it appears to be discarding the
session identifier appended to the URI). Its also doing a "HEAD" HTTP
request on each URI as well as a GET. As far as I know this alone should
not cause a problem, as Turbine does not process "HEAD" requests, but
it's a bit odd.
Anyway if you can identify what browser is being used, and any proxies
that are being used, then you've probably found the source of the
problem.
--
Sean Legassick
[EMAIL PROTECTED]
Ek is 'n man: niks menslik is vreemd vir my nie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
