Hi Lukas, I remember working on a project where we had this problem. I think it turned out to be an exception raised by a missing asset (image) when using with conjunction with LiipImagineCache. I don't remember the specific details to pinpoint to what extent was that relationship to blame (if any at all or just the 404), so I'll see if I can bring in more detail through the person who was working with me on this.
Regards, -- Rui Marinho seegno.com On Monday, October 22, 2012 3:03:09 PM UTC+1, Lukas Smith wrote: > > > On Oct 22, 2012, at 15:59 , ryan weaver <weave...@gmail.com <javascript:>> > wrote: > > > Hi Lukas! > > > > I personally haven't seen the 404->logout issue, though I'm familiar > with the issue outlined in that ticket. What is the connection between the > 404/403 problem in the ticket and the 404 causing a logout in your case? Do > you know what in the 404 process is actually triggering the logout? > > I havent investigated the actual cause. Johannes pointed me at the ticket, > so I assumed that its not an easy fix. > > regards, > Lukas Kahwe Smith > m...@pooteeweet.org <javascript:> > > > > -- 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 developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
