When you perform a server action and there is a navigate the defined headers on response gets lost

[AlbertSabate]

Example:

async function submitForm(
  e: JSX.TargetedSubmitEvent<EventTarget> & { formData: FormData },
  req: RequestContext,
) {
  setCookie(req, 'access-token', responseData.data.accessToken, { expires });
  navigate('/');
}

const Component = () => <form onSubmit={submitForm} />;

The cookie 'access-token' should be defined, but it's not.

[aralroca]

I don't know at what point it is an issue or it is better to create a feature of Brisa, cookies should be added to the response and not to the request.

[AlbertSabate]

Yep, correct. That was my fault. I meant response. So as you mentioned I followed https://brisa-mu.vercel.app/building-your-application/routing/middleware#on-response and make it work.

Example:

export function responseHeaders(req: RequestContext) {
  const headers: Record<string, string> = {};
  const accessToken = req.store.get('access-token') as string | undefined;
  if (accessToken) {
    const expires = new Date();
    expires.setTime(expires.getTime() + 518_400_000); // Cookie will expire in 6d
    headers['set-cookie'] = setCookie('access-token', accessToken, undefined, { expires });
  }

  return headers;
}

[aralroca]

For now we keep the responseHeaders to modify the headers of the actions