Illya's approach is pretty clean. I actually like it better than the symfony 1 solution I mentioned, and have since implemented it in both my sf1 and sf2 apps.
I wonder whether or not the framework itself should be the one to intelligently return a 403 or 401 rather than a 302 when the request is a XHR...but I'm not sure its appropriate 100% of the time. At least the event-driven approach is pretty efficient and simple. On Jun 9, 4:47 pm, Paul Dugas <p...@dugasenterprises.com> wrote: > On Wed, 2011-06-08 at 12:23 -0700, Illya Klymov wrote: > > I'm not sure about the "right" way, but what am i doing now, is > > hooking into 'core.exception', returning 403 error, and handling it > > wit JS (JQuery):https://gist.github.com/1015146 > > Bump. I'd love to hear from some of the core developers on whether this > approach is "correct" and, if not, what the "right" solution is. > > Paul > > signature.asc > < 1KViewDownload -- 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
