Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <blockquote> <p>EDIT >> I posted this answer in a blog post as well: <a href="http://zadasnotes.blogspot.com/2010/11/rails-3-forgery-csrf-protection-for.html" rel="noreferrer">http://zadasnotes.blogspot.com/2010/11/rails-3-forgery-csrf-protection-for.html</a></p> <p>EDIT 2 >> This was changed in Rails 3.0.4. See follow up post here: <a href="http://zadasnotes.blogspot.com/2011/02/rails-forgery-csrf-protection-for-ajax.html" rel="noreferrer">http://zadasnotes.blogspot.com/2011/02/rails-forgery-csrf-protection-for-ajax.html</a></p> </blockquote> </blockquote> <p>After researching it for a while, I decided to dig a bit into the rails code documentation to find out. </p> <p>Starting here: <a href="http://api.rubyonrails.org/classes/ActionController/RequestForgeryProtection.html#method-i-form_authenticity_token" rel="noreferrer">http://api.rubyonrails.org/classes/ActionController/RequestForgeryProtection.html#method-i-form_authenticity_token</a></p> <p><strong>protect_from_forgery</strong> adds a <strong>before_filter</strong> on <strong>verify_authenticity_token</strong> which is shown below: </p> <pre><code># File actionpack/lib/action_controller/metal/request_forgery_protection.rb, line 95 95: def verify_authenticity_token 96: verified_request? || raise(ActionController::InvalidAuthenticityToken) 97: end </code></pre> <p>And the <strong>verified_request?</strong> is shown here:</p> <pre><code># File actionpack/lib/action_controller/metal/request_forgery_protection.rb, line 104: def verified_request? 105: !protect_against_forgery? || request.forgery_whitelisted? || 106: form_authenticity_token == params[request_forgery_protection_token] 107: end </code></pre> <p>Finally <strong>request.forgery_whitelisted?</strong>:</p> <pre><code> # File actionpack/lib/action_dispatch/http/request.rb, line 126 126: def forgery_whitelisted? 127: get? || xhr? || content_mime_type.nil? || !content_mime_type.verify_request? 128: end </code></pre> <p>Notice <strong>xhr?</strong>. xmlHttpRequest is whitelisted and is not on the protect_from_forgery list. So it appears that this is by design. </p> <p>After researching further on xmlHttpRequests it appears that there are restrictions on running them across domains, which makes it unnecessary to apply the csrf check on xhr. </p>
    singulars
    1. This table or related slice is empty.
    1. PORails 3 AJAX request authenticity token ignored
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USzzawaideh
    1. USzzawaideh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORails 3 AJAX request authenticity token ignored
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis has changed as of Rails 3.0.4 - now AJAX requests also need to provide the token. See [this commit](https://github.com/rails/rails/commit/ae19e4141f27f80013c11e8b1da68e5c52c779ea)
      singulars
      1. PO
      1. USjamuraa
    2. CO@jamuraa Thanks for pointing it out. I had a follow-up blog post regard this here: http://zadasnotes.blogspot.com/2011/02/rails-forgery-csrf-protection-for-ajax.html
      singulars
      1. PO
      1. USzzawaideh
    3. COnone of above links for zadasnotes.blogspot.com work....
      singulars
      1. PO
      1. USSwapnil Chincholkar
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload