It works on Firefox therefore it is not server side. Regardless we fixed the problem.
On Mon, Jan 24, 2011 at 5:33 PM, Eric B. <ebe...@hotmail.com> wrote: > I remember back in the early days of Chrome I used to have problems with > JS and Ajax as well. But the newer versions seemed to have resolve the > problems that I was encountering. > > Have you checked if the problem is Chrome to executing the JS properly, or > if it is a server side issue in which the filter is not properly executed? > Are the Chrome AJAX request properly setting the XML HTTP header? (in > theory, given that it is JQ, it should all be standard, but you never > know....). > > I assume you have a separate mechanism for session timeouts; are the > requests from Chrome properly handled? > > Off the top of my head, my first instinct would be to indicate that Chrome > JS isn't doing it's job properly, but there may also be a case where you > might be getting double ajax submissions/requests and your session > monitoring may not properly be handling the double requests (I also had a > problem with double requests in the early days of Chrome). > > Have you been able to isolate where the exact problem is occurring? > > Tx, > > Eric > > > "Gareth McCumskey" <gmccums...@gmail.com> wrote in message > news:aanlktim3dwnxbjq-ftg4uo8of6cjd9uptuhyv8073...@mail.gmail.com... > Hi all, > > I have interesting problem. Something we have all encountered before ... > browser inconsistencies. This is related to handling session timeouts on an > ajax request. I'll just layout our current setup. > > We have a symfony filter that detects whether the current request is an XML > HTTP Request and if the current user session has timed out. The code for > this is: > > if ($user->isAuthenticated() == false && $request->isXmlHttpRequest()) > { > return $context->getController()->redirect('users/ajaxTimeout'); > exit; > } > > As you can see if the IF conditions are met it redirects to another action > whose code is: > > sfContext::getInstance()->getResponse()->setHttpHeader("Content-Type", > "application/json"); > return $this->renderText(json_encode(array("error"=>"session", > "url"=>"users/login"))); > > We also have our jQuery .ajaxSetup as follows on the success callback: > > success : function(response, textStatus, xmlobject) { > try { > var json_res = jQuery.parseJSON(response); > if (json_res.error == "session") > { > window.location.href = json_res.url; > } > } > catch (e) > { > > } > > The workflow is that as soon as an ajax request is made, the filter catches > the request, and detects the request is AJAX and session has timed out so > redirects the request to the action code above. The action responds with a > JSON string which the global .ajaxSetup success callback catches and sees > that there is a session error and redirects the entire page to the login > screen. > > It works well in Firefox and IE however in Chrome it doesn't. I was > wondering if anyone here might have some insight into what might be causing > the problem. > > -- > Gareth McCumskey > http://garethmccumskey.blogspot.com > twitter: @garethmcc > identi.ca: @garethmcc > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc identi.ca: @garethmcc -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
