Re: [symfony-users] Re: Handling AccessDeniedException

2011-06-06 Thread Paul Dugas
Tried setting _format to json in your route? I believe that will trigger the framework to render the exception using the json.twig template in vendor/symfony/src/Symfony/Bundle/FrameworkBundle/Resources/views/Exception though I may be off-base on that. On Mon, 2011-06-06 at 02:52 -0700, winzou w

[symfony-users] Re: Handling AccessDeniedException

2011-06-06 Thread winzou
Hi, I'm still stuck on this. Any idea? Thanks -- 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 symf

[symfony-users] Re: Handling AccessDeniedException

2011-06-02 Thread winzou
Thank you for your answer, but it's not the point. You're right, in theory, an AJAX request should not face an AccessDeniedException. But I'm just playing with the framework, and wanted to see the behavior "in case of". So I throw my AccessDeniedException on purpose, for me to make a javascript

[symfony-users] Re: Handling AccessDeniedException

2011-06-02 Thread Roger Webb
Your AJAX request will use the same cookie/authentication as you use normally. I would check the access control on the route you are POSTing to with your AJAX request. My guess is that you are having an issue with ROLEs or user type. Remember that firewalls/access control (ROLES) can (and often