On Apr 10, 7:48 am, Tom Gregory <[EMAIL PROTECTED]> wrote: > That's mostly true. Redirect headers (e.g., 301, 302), are handled > transparently by the browser, so your Javascript will never see 'em. > > TAG > > On Apr 10, 2007, at 6:47 AM, 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.
Thanks for all the comments. My handler (modperl) returns a redirect header with HTTP 302. However, unlike how you describe it, the login page actually appears in the <div> where the response text should ideally appear when the credentials are still valid, which leads me to think that JavaScript (and not the browser) still has control of what's returned. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
