Continuing this conversation I'm having with myself ... Most forms should be testable using getAndCheck, setField, click ... which will submit the CSRF token and work just fine. So nevermind (again).
k On May 24, 8:09 am, Kris Wallsmith <[EMAIL PROTECTED]> wrote: > Oh, nevermind. I can just update settings.yml... > > test: > .settings: > csrf_secret: off > > Maybe this should this be part of the skeleton settings.yml that's > created by generate:app? > > On May 24, 7:51 am, Kris Wallsmith <[EMAIL PROTECTED]> wrote: > > > Piggybacking on my previous post on CSRF protection ... what's the > > best way to disable CSRF protection for my functional tests? I've > > added a condition to frontendConfiguration::initialize() that disables > > protection in the test environment, but I'd rather not add logic the > > only runs for test... > > > Any suggestions? > > > Thanks, > > Kris --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
