Databases
StackOverflow2013
Postsdbo
PORails - Losing session with Integration Tests and Capybara - CSRF related?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails - Losing session with Integration Tests and Capybara - CSRF related?
    primarykey
    data
    text
    <p>I'm using Rails 3.1.0.rc4 and I'm working on doing integration tests with capybara's new Steak-like DSL and Rspec (using Devise authentication)</p> <p>The issue I'm having is that when I run an integration test, the rack-test driver from capybara seems to just completely lose the user's logged in session, in fact, the session seems to just clear out altogether.</p> <p>After days of debugging, I'm at a complete loss as to why. Going line by line through the middleware stack, I believe I've ruled the problem down to something going on in the <code>ActiveRecord::SessionStore</code> that is causing this. I've read <a href="https://stackoverflow.com/questions/5000333/how-does-rails-csrf-protection-work">here</a> that Rails will clear out a session if it can't validate the CSRF token, which leaves me to believe that I've got something configured wrong, and for some reason this one test is not authenticating the CSRF token correctly.</p> <p>This is what is in my session_store.rb in the /initializers directory:</p> <pre><code>MyApp::Application.config.session_store :active_record_store </code></pre> <p>Does anyone who knows about CSRF protection in rails have any leads on why this may be happening? </p> <p>Also, here are some things to note:</p> <ul> <li>the thing I'm trying to test actually works within the browser itself, only this one test is dropping the session</li> <li>the session seems to get dropped after the submission of a form to which the action url is to another server. I'm using the VCR gem for capturing the requests/responses to this external server in the test, and while I believe I've ruled the external request as the problem, this may have something directly to do with the CSRF token not authenticating, thus clearing out the session.</li> <li>other tests involving logging in / using sessions are not dropping sessions</li> </ul> <p>Can anyone give me any leads as to what is going on here exactly, and why the one test just seems to arbitrarily drop its session and fail on me? I've done lots of debugging and have tried everything I can possible think of.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USjoeellis
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails - Losing session with Integration Tests and Capybara - CSRF related?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails - Losing session with Integration Tests and Capybara - CSRF related?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails - Losing session with Integration Tests and Capybara - CSRF related?
      1. USJohn
      1. VTFavorite
    1. COIm having the same issue... argh...
      singulars
      1. PORails - Losing session with Integration Tests and Capybara - CSRF related?
      1. USLichtamberg
 

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