#Browser Cookie

2 messages · Page 1 of 1 (latest)

graceful kite
#

In my Qwik JS + Axios + Fiber (Go) project, I’m trying to store authentication cookies (access_token & refresh_token) in the browser after a successful login.

My backend (Fiber v3) sets cookies using Set-Cookie with HttpOnly, SameSite=Lax, and AllowCredentials=true in CORS.

When I call the login API directly from a browser-side function using axios.post(..., { withCredentials: true }), the cookies are stored correctly in the browser.

However, when I perform the same request inside a Qwik routeAction$, the cookies are not stored.

So my questions are:

What is the recommended or ideal way in Qwik to perform login so that backend cookies are stored in the browser?

Should login be handled through a routeAction$, or should it always be done inside a $() function (client-side)?

If routeAction$ is preferred, how can I forward Set-Cookie headers from the backend to the browser correctly?

eternal steppe