rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: oilpastels <resplence@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: attack prevented by Rack::Protection::RemoteToken
Date: Thu, 8 Dec 2011 15:54:55 -0800 (PST)	[thread overview]
Message-ID: <362bf00c-5025-4dbd-a52f-9c7cda5dcc02@e19g2000yqk.googlegroups.com> (raw)
In-Reply-To: <2bab7814-f4d4-4974-87c2-1fbe3bd546a2@p14g2000yqp.googlegroups.com>

The problem is exactly what mateo described. I spoke with Konstantin
Haase, the maintainer of the rack-protection gem referenced by Evgeni
above, and he instructed me to:

> set :protection, :except => [:remote_token, :frame_options]

And it worked.

On Dec 8, 7:24 pm, mateo <mateo.mur...@gmail.com> wrote:
> Facebook requests pages via POST, and since the referrer is different,
> it's tripping up your app's CSRF protection
>
> On Dec 8, 10:29 am, oilpastels <resple...@gmail.com> wrote:
>
>
>
>
>
>
>
> > I have a sinatra app that works fine on Heroku, but when requested as
> > a page tab on facebook returns blank, and the logs read "attack
> > prevented by Rack::Protection::RemoteToken". What is this about?

  reply	other threads:[~2011-12-08 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 15:29 attack prevented by Rack::Protection::RemoteToken oilpastels
2011-12-08 17:20 ` Evgeni Dzhelyov
2011-12-08 21:24 ` mateo
2011-12-08 23:54   ` oilpastels [this message]
2012-02-24 13:50     ` vzmind

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=362bf00c-5025-4dbd-a52f-9c7cda5dcc02@e19g2000yqk.googlegroups.com \
    --to=rack-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).