Closed hitesh-sourcefuse closed 1 month ago
If you use '# @no-cookie-jar', no cookies will be sent and the cookies received will not be reused for further requests. CookieJar support is completely deactivated. Why do you actually need # @no-cookie-jar
? @ref
actually ensures that the request is not called more than once. In other words, as long as you do not call up the login again manually, the request would actually be without a cookie. And if you want to delete the cookie manually, it would be stored in the UserStore and can be deleted (or just reset environment).
For the first request I wanted to use no cookies so that when API hit will have the fresh data set. The issue is resolved after removing the @no-cookie-jar
and making the cooking non-secure.
I will close the issue, BTW screenshot was much help to know where I can see the current cookies.
Thanks
Using in the VS Code extension with the setting for the cookies Jar as Enabled
When running a Preference request, it is not using the Cookie set by the login API which got called first, as it refers to it. API responses are in console is as following: