True, that would be better *scurries off to update code*
-- Dash --
Michael Peters wrote:
> David Dashifen Kees wrote:
>
>> Don't know what you're sever side environment is, but if you explicitly
>> create and HTTP status code other than 200 (or any in the 200's) the
>> prototype Ajax objects will call their onFailure function. So, in PHP
>> you could do this:
>>
>> header("HTTP/1.0 403 Forbidden");
>>
>> And, on the client side, the Ajax object would fire the onFailure
>> routine which could then be used to repaint the screen or force a
>> re-login or whatever.
>>
>
> Even better would be to set an 'on403' handler to specifically handle auth
> failures rather than treating all failures as auth failures.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
