after ac.cookie.set() ac.cookie.get() returns "undefined" - bug? about mojito HOT 3 CLOSED

Hi,

Thanks for reporting this. To my understanding this is the expected behavior; ac.cookie.get gets the cookies from the request, whereas ac.cookie.set sets new cookies for the response. So when you call ac.cookie.set the client will get the new cookie, but when you call ac.cookie.get right after, the cookies returned should be the original set of cookies that the client sent, not the new cookies that will be sent back. This is slightly different from what you would expect when using Y.Cookie on the client side. Let me know if you have any questions.

Thanks,
Albert

from mojito.

Hi,
Thank you for the anwser. What I try to do is to make sure whether cookie was set (and its value) or not in single execution of server controller code where app logic needs this confimation because I want link some server stored data with it - ie implement sessions.btw. implementation ac.cookie.get() changed recently? Mojito sessions https://github.com/akshar100/mojito-session addon which was starting point for me uses it "wrong way".

from mojito.

Based on the history of cookie.server.js, the implementation has been the same since 2012. I am not familiar with mojito-session, but if you end up creating your own solution, you may consider open sourcing it so others can benefit from it.

from mojito.