Django login redirect_field_name 'next' forces new session
I'm building an e-commerce website, I enable guest users to add products to their carts saving the cart_id
in session and when they proceed to checkout, I redirect them to login as follows inside the checkout view
if not request.user.is_authenticated:
login_url = reverse('accounts:login')
check_out_url = reverse('cart:checkout')
redirect_url = "{}?next={}".format(login_url, check_out_url)
return redirect(redirect_url)
# checkout process here
It works, however the cart_id
is no longer in the session.
If I don't use the next parameter and just redirect to login_url
the cart_id
stays in session.
P.S:
Same thing happens with login_required_decorator
Is there a way to keep the session data intact ?
django django-views django-login
add a comment |
I'm building an e-commerce website, I enable guest users to add products to their carts saving the cart_id
in session and when they proceed to checkout, I redirect them to login as follows inside the checkout view
if not request.user.is_authenticated:
login_url = reverse('accounts:login')
check_out_url = reverse('cart:checkout')
redirect_url = "{}?next={}".format(login_url, check_out_url)
return redirect(redirect_url)
# checkout process here
It works, however the cart_id
is no longer in the session.
If I don't use the next parameter and just redirect to login_url
the cart_id
stays in session.
P.S:
Same thing happens with login_required_decorator
Is there a way to keep the session data intact ?
django django-views django-login
add a comment |
I'm building an e-commerce website, I enable guest users to add products to their carts saving the cart_id
in session and when they proceed to checkout, I redirect them to login as follows inside the checkout view
if not request.user.is_authenticated:
login_url = reverse('accounts:login')
check_out_url = reverse('cart:checkout')
redirect_url = "{}?next={}".format(login_url, check_out_url)
return redirect(redirect_url)
# checkout process here
It works, however the cart_id
is no longer in the session.
If I don't use the next parameter and just redirect to login_url
the cart_id
stays in session.
P.S:
Same thing happens with login_required_decorator
Is there a way to keep the session data intact ?
django django-views django-login
I'm building an e-commerce website, I enable guest users to add products to their carts saving the cart_id
in session and when they proceed to checkout, I redirect them to login as follows inside the checkout view
if not request.user.is_authenticated:
login_url = reverse('accounts:login')
check_out_url = reverse('cart:checkout')
redirect_url = "{}?next={}".format(login_url, check_out_url)
return redirect(redirect_url)
# checkout process here
It works, however the cart_id
is no longer in the session.
If I don't use the next parameter and just redirect to login_url
the cart_id
stays in session.
P.S:
Same thing happens with login_required_decorator
Is there a way to keep the session data intact ?
django django-views django-login
django django-views django-login
asked Nov 21 '18 at 13:28
Zeyad Obaia
106212
106212
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
We'd need more info to know for sure, but here's a best guess based on experience:
Are you sure the redirect is taking you to the same domain, in cookie terms?
eg, if you're authenticated on foo.somedomain.com
and the next
references www.somedomain.com
, then Django (by default) will want to use separate cookies for those two, separate domains.
To make Django use a cookie across all subdomains for a given domain, you'll want to set settings.SESSION_COOKIE_DOMAIN
(docs) to just the domain. eg somedomain.com
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%2f53413106%2fdjango-login-redirect-field-name-next-forces-new-session%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
We'd need more info to know for sure, but here's a best guess based on experience:
Are you sure the redirect is taking you to the same domain, in cookie terms?
eg, if you're authenticated on foo.somedomain.com
and the next
references www.somedomain.com
, then Django (by default) will want to use separate cookies for those two, separate domains.
To make Django use a cookie across all subdomains for a given domain, you'll want to set settings.SESSION_COOKIE_DOMAIN
(docs) to just the domain. eg somedomain.com
add a comment |
We'd need more info to know for sure, but here's a best guess based on experience:
Are you sure the redirect is taking you to the same domain, in cookie terms?
eg, if you're authenticated on foo.somedomain.com
and the next
references www.somedomain.com
, then Django (by default) will want to use separate cookies for those two, separate domains.
To make Django use a cookie across all subdomains for a given domain, you'll want to set settings.SESSION_COOKIE_DOMAIN
(docs) to just the domain. eg somedomain.com
add a comment |
We'd need more info to know for sure, but here's a best guess based on experience:
Are you sure the redirect is taking you to the same domain, in cookie terms?
eg, if you're authenticated on foo.somedomain.com
and the next
references www.somedomain.com
, then Django (by default) will want to use separate cookies for those two, separate domains.
To make Django use a cookie across all subdomains for a given domain, you'll want to set settings.SESSION_COOKIE_DOMAIN
(docs) to just the domain. eg somedomain.com
We'd need more info to know for sure, but here's a best guess based on experience:
Are you sure the redirect is taking you to the same domain, in cookie terms?
eg, if you're authenticated on foo.somedomain.com
and the next
references www.somedomain.com
, then Django (by default) will want to use separate cookies for those two, separate domains.
To make Django use a cookie across all subdomains for a given domain, you'll want to set settings.SESSION_COOKIE_DOMAIN
(docs) to just the domain. eg somedomain.com
answered Nov 21 '18 at 13:34
Steve Jalim
9,7952744
9,7952744
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53413106%2fdjango-login-redirect-field-name-next-forces-new-session%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