Mixing
Django Password Reset generating http link instead of https
I am using Django's inbuilt password reset mechanism. It sends an email with a link containing a token, which when clicked can be used to reset the password. However, the link being generated is using the template:
{% trans "Please go to the following page and choose a new password:" %}
{% block reset_link %}
{{ protocol }}://{{ domain }}{% url 'password_reset_confirm' uidb64=uid token=token %}
{% endblock %}
Here, the {{ protocol }} is returning http instead of https.
My nginx server would redirect any http requests to the https base link (the homepage).
Hence, the password reset link does not work since the link generated is wrong. It simply goes to the homepage via nginx.
How do I fix this?
django python-3.x nginx
asked Jan 2 at 18:14
Yash MittraYash Mittra
415
add a comment |
I am using Django's inbuilt password reset mechanism. It sends an email with a link containing a token, which when clicked can be used to reset the password. However, the link being generated is using the template:
{% trans "Please go to the following page and choose a new password:" %}
{% block reset_link %}
{{ protocol }}://{{ domain }}{% url 'password_reset_confirm' uidb64=uid token=token %}
{% endblock %}
Here, the {{ protocol }} is returning http instead of https.
My nginx server would redirect any http requests to the https base link (the homepage).
Hence, the password reset link does not work since the link generated is wrong. It simply goes to the homepage via nginx.
How do I fix this?
django python-3.x nginx
asked Jan 2 at 18:14
Yash MittraYash Mittra
415
add a comment |
I am using Django's inbuilt password reset mechanism. It sends an email with a link containing a token, which when clicked can be used to reset the password. However, the link being generated is using the template:
{% trans "Please go to the following page and choose a new password:" %}
{% block reset_link %}
{{ protocol }}://{{ domain }}{% url 'password_reset_confirm' uidb64=uid token=token %}
{% endblock %}
Here, the {{ protocol }} is returning http instead of https.
My nginx server would redirect any http requests to the https base link (the homepage).
Hence, the password reset link does not work since the link generated is wrong. It simply goes to the homepage via nginx.
How do I fix this?
django python-3.x nginx
asked Jan 2 at 18:14
Yash MittraYash Mittra
415
I am using Django's inbuilt password reset mechanism. It sends an email with a link containing a token, which when clicked can be used to reset the password. However, the link being generated is using the template:
{% trans "Please go to the following page and choose a new password:" %}
{% block reset_link %}
{{ protocol }}://{{ domain }}{% url 'password_reset_confirm' uidb64=uid token=token %}
{% endblock %}
Here, the {{ protocol }} is returning http instead of https.
My nginx server would redirect any http requests to the https base link (the homepage).
Hence, the password reset link does not work since the link generated is wrong. It simply goes to the homepage via nginx.
How do I fix this?
django python-3.x nginx
django python-3.x nginx
asked Jan 2 at 18:14
Yash MittraYash Mittra
415
asked Jan 2 at 18:14
Yash MittraYash Mittra
415
asked Jan 2 at 18:14
Yash MittraYash Mittra
415
asked Jan 2 at 18:14
Yash MittraYash Mittra
415
asked Jan 2 at 18:14
Yash MittraYash Mittra
415
415
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is likely an issue with X-Forwarded-Protocol in your nginx config.
You need to add this inside your location block:
proxy_redirect off;
proxy_set_header X-Forwarded-Proto $scheme;
For more info see: https://djangodeployment.com/2017/01/24/fix-djangos-https-redirects-nginx/
answered Jan 2 at 18:22
Hairy ChrisHairy Chris
1,1871223
This is the correct answer, if it helped you out will you please mark it as 'accepted'.
– Hairy Chris
Jan 11 at 12:05
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011207%2fdjango-password-reset-generating-http-link-instead-of-https%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is likely an issue with X-Forwarded-Protocol in your nginx config.
You need to add this inside your location block:
proxy_redirect off;
proxy_set_header X-Forwarded-Proto $scheme;
For more info see: https://djangodeployment.com/2017/01/24/fix-djangos-https-redirects-nginx/
answered Jan 2 at 18:22
Hairy ChrisHairy Chris
1,1871223
This is the correct answer, if it helped you out will you please mark it as 'accepted'.
– Hairy Chris
Jan 11 at 12:05
add a comment |
This is likely an issue with X-Forwarded-Protocol in your nginx config.
You need to add this inside your location block:
proxy_redirect off;
proxy_set_header X-Forwarded-Proto $scheme;
For more info see: https://djangodeployment.com/2017/01/24/fix-djangos-https-redirects-nginx/
answered Jan 2 at 18:22
Hairy ChrisHairy Chris
1,1871223
This is the correct answer, if it helped you out will you please mark it as 'accepted'.
– Hairy Chris
Jan 11 at 12:05
add a comment |
This is likely an issue with X-Forwarded-Protocol in your nginx config.
You need to add this inside your location block:
proxy_redirect off;
proxy_set_header X-Forwarded-Proto $scheme;
For more info see: https://djangodeployment.com/2017/01/24/fix-djangos-https-redirects-nginx/
answered Jan 2 at 18:22
Hairy ChrisHairy Chris
1,1871223
This is likely an issue with X-Forwarded-Protocol in your nginx config.
You need to add this inside your location block:
proxy_redirect off;
proxy_set_header X-Forwarded-Proto $scheme;
For more info see: https://djangodeployment.com/2017/01/24/fix-djangos-https-redirects-nginx/
answered Jan 2 at 18:22
Hairy ChrisHairy Chris
1,1871223
answered Jan 2 at 18:22
Hairy ChrisHairy Chris
1,1871223
answered Jan 2 at 18:22
Hairy ChrisHairy Chris
1,1871223
answered Jan 2 at 18:22
Hairy ChrisHairy Chris
1,1871223
1,1871223
This is the correct answer, if it helped you out will you please mark it as 'accepted'.
– Hairy Chris
Jan 11 at 12:05
add a comment |
This is the correct answer, if it helped you out will you please mark it as 'accepted'.
– Hairy Chris
Jan 11 at 12:05
This is the correct answer, if it helped you out will you please mark it as 'accepted'.
– Hairy Chris
Jan 11 at 12:05
This is the correct answer, if it helped you out will you please mark it as 'accepted'.
– Hairy Chris
Jan 11 at 12:05
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011207%2fdjango-password-reset-generating-http-link-instead-of-https%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
