# Exception\_logger and protect\_from\_forgery

**URL:** <https://www.ruby-forum.com/t/exception-logger-and-protect-from-forgery/149305>\
**Category:** Rails\
**Created:** [September 23, 2008, 1:10pm UTC](https://www.ruby-forum.com/t/exception-logger-and-protect-from-forgery/149305 "2008-09-23T13:10:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![phil](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/e95f7d/32.png) [@phil](https://www.ruby-forum.com/u/phil)\
**Post date:** [September 23, 2008, 1:10pm UTC](https://www.ruby-forum.com/t/exception-logger-and-protect-from-forgery/149305/1 "2008-09-23T13:10:34Z")

</div>

I am having a problem using the exception\_logger plugin when I have  
protect\_from\_forgery enabled.

Here is the line from application.rb:  
protect\_from\_forgery :secret =\> ‘xxxx’

But I am getting:  
No :secret given to the #protect\_from\_forgery call. Set that or use a  
session store capable of generating its own keys (Cookie Session  
Store).

Now, if I remove the secret and try and use MY controllers I get that  
error, but it goes away when the secret is there.

Any ideas what the issue is?