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 ?










share|improve this question


























    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 ?










    share|improve this question
























      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 ?










      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 at 13:28









      Zeyad Obaia

      101212




      101212
























          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






          share|improve this answer





















            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',
            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
            });


            }
            });














             

            draft saved


            draft discarded


















            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








            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






            share|improve this answer

























              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






              share|improve this answer























                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






                share|improve this answer












                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







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 21 at 13:34









                Steve Jalim

                9,7452743




                9,7452743






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    Contact image not getting when fetch all contact list from iPhone by CNContact

                    count number of partitions of a set with n elements into k subsets

                    A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks