Do you have it set up to redirect to the SSL version in production? It's possible that it's configured per-environment and you haven't disabled it for the test environment.
On Thursday, November 8, 2012 at 3:21 PM, Andrew Beckwith wrote:
> Following your theory, I opened the developer tools Network pane, and watched - and you are right, it was doing a redirect to itself before forwarding on to /users/sign_in
> So I tried cutting to the chase: visit '/users/sign_in'
> Scenario: Activate listing # features/create_whitelist.feature:15
> 2012-11-08 14:15:49.124 webkit_server[23510:307] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead. > Finished "EnableLogging" with response "Success()" > Wrote response true "" > Received "Visit" > Started "Visit" > Load started > "Visit" started page load > Started request to "http://127.0.0.1:63656/users/sign_in" > Finished "Visit" with response "Success()" > Received 301 from "http://127.0.0.1:63656/users/sign_in" > 0 requests remaining > Started request to "https://127.0.0.1:63656/users/sign_in" > Received 0 from "https://127.0.0.1:63656/users/sign_in" > 0 requests remaining > Page finished with false > Load finished > Page load from command finished > Wrote response false "Unable to load URL: http://127.0.0.1:63656/users/sign_in because of error loading https://127.0.0.1:63656/users/sign_in: Connection closed" > Given I have successfully logged in as an operator # features/step_definitions/base_steps.rb:1
> Unable to load URL: http://127.0.0.1:63656/users/sign_in because of error loading https://127.0.0.1:63656/users/sign_in: Connection closed (Capybara::Webkit::InvalidResponseError)
> ./features/step_definitions/base_steps.rb:2:in `/^I have successfully logged in as an ([^"]*)$/'
> features/create_whitelist.feature:16:in `Given I have successfully logged in as an operator'
> Do you know why (or am I missing something) it is trying the SSL url? There obviously isn't one running... When I follow this in Chrome's dev tools, there is no redirect happening when I go direct to /users/sign_in