Right, I was suggesting you make a change on your server so you don't send a 3xx redirection, and instead send another code that you can check for on the client. You could still do the redirection from javascript.
There was just another thread about detecting URL redirections in ajax. Seems it's possible in firefox, but not safari, and I don't know about other browsers. --Erik On 9/18/07, dougXN <[EMAIL PROTECTED]> wrote: > > > I thought the status code would work, but the status code that returns > does not say anything about being redirected. It all comes back very > normal like it did something that it was suppose to do..... > > Actually the status code seems to be a bit disappointing in general. > It would be easiest if it just had a returning url property.... > > cheers > dn > > > On Sep 18, 2:12 pm, "Erik Beeson" <[EMAIL PROTECTED]> wrote: > > Ick, don't check the content. That's very ugly. You could always return > JSON > > objects that include status information, or better yet, use HTTP status > > codes. > > > > I'll provide an example in a new thread. > > > > --Erik > > > > On 9/18/07, dougXN <[EMAIL PROTECTED]> wrote: > > > > > > > > > We have a website that requires login. When we go to the site, if the > > > login has expired we get a screen that logs us in, then redirects us > > > to our initial request. > > > > > The problem is that if the request is a jquery/ajax .load(...., > > > 'mydiv'), it does not go into the div it justs loaded the whole bloody > > > page into the window, thus ruining the page setup. > > > > > I think the answer is to check the returning page source and then > > > either reload the page or continue depending if I am logged on or not. > > > > > Anyone have any ideas how to accomplish this in a jquery sort of way? > > > > > thanks > > > dn > >
