Set mailer default URL protocol to HTTPS #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not sure what happened to
Gemfile.lock, but the code inconfig/environments/development.rbsets the default protocol for the account activation (and all other) email links to HTTPS (I had to edit the "host" variable to get the links to work on my workspace). Previously, the default was HTTP, and upon clicking the link I was redirected to the homepage (with the "Invalid activation link" behavior), but the new user's "activated" attribute was set to "true" (verified with the rails console before and after visiting the URL) and I was able to log in without any redirects, error messages, etc. All tests have passed before and after this implementation.This behavior occurred using Rails 4.2.2 with the Cloud9 IDE in Google Chrome.