Actually, I think that in this case: the browser try to access favicon.ico as favicon.ico doesn't exist, apache redirect the request to index.php and so if you aren't logged in you see sfGuardAuth/signin before see a 404 because the referer is the favicon.
Perhaps because of a 'all: is_secure: on' ? Le 10/09/09 10:37, Fabrice B a écrit : > I experienced the same as Thomas. > > The solution, it seems, would be to edit your sfGuardAuth module to > remove any forwarding to the referer. > > But I still don't understand how symfony can actually reference the > favicon url as a referer ! I have not taken the time to verify if the > favicon.ico url is actually stored in the $_SERVER['HTTP_REFERER'] or > if this is a second effect of some symfony magic... > > Fabrice > -- > http://www.theodo.fr > > On Sep 10, 12:02 am, Thomas Rabaix<thomas.rab...@gmail.com> wrote: > >> looks to me the sfGuardPlugin keeps the last referer to your favicon url. >> This can happen if the file does not exist, then symfony catch the call. >> Your app require authentication, so guard plugin keep the referer as the >> favicon. >> >> So next time you login it works... >> >> The favicon call can be done randomly by the web browser that why the >> problem is intermittent. >> >> >> >> >> >> On Wed, Sep 9, 2009 at 10:48 PM, Jake Barnes<lkrub...@geocities.com> wrote: >> >> >>>> An easy fix for your problem is adding a favicon.ico to your document >>>> root. Also make sure that the login page doesn't require any other >>>> images that do not exist on the server. >>>> >> >>> I'm sorry if I wasn't clear, but I've already tried this. Now what >>> happens is that you fill in your username and password and then you >>> hit submit and then you end up looking at an URL like this: >>> >> >>> http://www.mydomain.com/favicon.ico >>> >> >>> At which point, you can see the favicon, but that is all you can see, >>> because that is where the browser is now pointing. >>> >> >>> If you log out, and then log back in, the problem vanishes. As I said >>> before, the problem is intermittent. >>> >> >>> ---- lawrence >>> >> >>> On Sep 9, 5:36 am, Bernhard Schussek<bschus...@gmail.com> wrote: >>> >>>> Hi Jake, >>>> >> >>>> Can you try to access the favicon directly on the server? The problem >>>> probably is that the favicon is requested by the login page. Instead >>>> of loading an image, the symfony stack is launched, redirects to the >>>> login page and stores the requested page in the session, which was the >>>> favicon. >>>> >> >>>> Once you sign in successfully, symfony recalls the remembered page and >>>> redirects to it. >>>> >> >>>> An easy fix for your problem is adding a favicon.ico to your document >>>> root. Also make sure that the login page doesn't require any other >>>> images that do not exist on the server. >>>> >> >>>> Bernhard >>>> -- >>>> Software Architect& Engineer >>>> Blog:http://webmozarts.com >>>> >> -- >> Thomas Rabaixhttp://rabaix.net >> > > > -- Tugdual SAUNIER --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---