[Seaside] 302 error
Timothy James Ziebart
timothy at churchmilitant.org
Thu Apr 15 04:44:52 UTC 2010
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?
Tim
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?
>
> Lukas
>
>
More information about the seaside
mailing list