[Seaside] 302 error
Timothy James Ziebart
timothy at churchmilitant.org
Thu Apr 15 05:11:08 UTC 2010
Ok it appears that a failure in retrieving records from a remote server
is causing the problem. There is an error and it appears to clobber
the session causing it to expire. I need to catch the error. Good
catch Lukas mentioning the session expiration. Thank you.
On 10-04-14 09:44 PM, Timothy James Ziebart wrote:
> I will try it with Kom. The events occur quite quickly so unless the
> setting for session expiration is somehow set to less than 5 minutes.
> Is that possible?
> On 10-04-14 09:41 PM, Lukas Renggli wrote:
>>> The div identified by 's_results' is where the dispatcher page will be
>>> displayed when onChange is triggerred. The console in firebug
>>> identifies it
>>> as a 302 error. If I continue the server will throw a 500 error. If I
>>> restart the session and do the same steps the error will not
>>> occur. Using
>>> Swazoo server.
>> Very strange. Is it the session that expires?
>> Can you reproduce the problem with Kom?
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside