You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2024. It is now read-only.
We have config.force_ssl = true across all envs and while migrating to request specs everything was getting HTTP 301/307s. I finally realised the specs were making HTTP requests, not HTTPS and with a bunch more digging we summarised our experience/fix here:
Some mention of how to ensure HTTPS requests are used in the specs would be great. There was very little information anywhere on this topic. And if one needs to use _url rather than _path helpers would strengthen this very useful chapter.
Thanks for your work on this book regardless, it's been invaluable.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have
config.force_ssl = true
across all envs and while migrating to request specs everything was getting HTTP 301/307s. I finally realised the specs were making HTTP requests, not HTTPS and with a bunch more digging we summarised our experience/fix here:https://stackoverflow.com/questions/6785261/test-an-https-ssl-request-in-rspec-rails/62552995#62552995
Some mention of how to ensure HTTPS requests are used in the specs would be great. There was very little information anywhere on this topic. And if one needs to use _url rather than _path helpers would strengthen this very useful chapter.
Thanks for your work on this book regardless, it's been invaluable.
The text was updated successfully, but these errors were encountered: