Django login redirect_field_name 'next' forces new session
up vote
0
down vote
favorite
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 |
up vote
0
down vote
favorite
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 |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
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 at 13:28
Zeyad Obaia
101212
101212
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
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 |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
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 |
up vote
0
down vote
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 |
up vote
0
down vote
up vote
0
down vote
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 at 13:34
Steve Jalim
9,7452743
9,7452743
add a comment |
add a comment |
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