Redirect Loop

Hi All,

one of our clients is complaining that intermittently they are receiving
a "Redirect Loop" error in their browses on one of our apps.

I've done some investigative work (i.e. put "self halt" in
WADispatcher>>#handleRequest:) and I can see that sometimes Seaside is
redirecting as many as 18-21 times for a simple GET url
(/seaside/myapp)? This can't be right, can it?

There are no callbacks/calls/answers at this point, just a simple page
rendering.

Any pointers on where I should look?

Many thanks,
John.


Consider your responsibility to the environment - think before you print!

******************************************************************************************************************************************
This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. *******************************************************************************************************************************************


Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2009/7/28 John Thornborrow <[hidden email]>:
Something like 15 tasks on a page could exhibit such a behavior.
Broken exception handling or a bug in session cookie initialization
are other options that come to my mind. To be sure set a breakpoint in
WAResponse >> #redirectTo: and you should see who is doing all these
redirects.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Thanks, I'm sure something is broken but I'm yet to see where. This
should help. :)

J.

Philippe Marschall wrote:

Consider your responsibility to the environment - think before you print!

******************************************************************************************************************************************
This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. *******************************************************************************************************************************************


Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside