Hi all,<br><br>I'm running up against the "page/action cacheing vs forgery-protection" issue described in various places eg here: <a href="http://mandarinsoda.com/2008/01/29/stupid-rails-mistakes-caching-and-authenticity-tokens/" target="_blank">http://mandarinsoda.com/2008/01/29/stupid-rails-mistakes-caching-and-authenticity-tokens/</a><br>

<br>Now - all the "solutions" that seem to be available say "turn off
forgery protection"... but surely that isn't the only option out
there. It seems so drastic (and dangerous).<br><br>Is there no way to render a form without the authenticity token? No other ideas?<br>
<br>Any ideas welcome :)<br><br>Cheers,<br><font color="#888888">Taryn<br></font>