kit: `cookies.delete` not working when using form `enhance`

Mhm then maybe this is a bug with deleting cookies after all…

@s3812497 i haven’t used the new cookies.delete function, but i am able to use cookies.set to remove a cookie:

cookies.set("cookieName", "", {
    httpOnly: true,
    path: '/',
    maxAge: 0
  })

@s3812497 Not solving for now, just trying to diagnose. Can you try this, and see whether it works as you intend? In src/routes/somewhere/+page.server.ts add the options parameter to cookies.delete with the path set…

import type { PageServerLoad } from "./$types";

export const load: PageServerLoad = ({ cookies }) => {
  // added options with path to both lines
  cookies.delete("cookie1", {path: '/'}); 
  cookies.delete("cookie2", {path: '/'});
};

This works for me (but I may be missing the point. )

It works as expected.

I have tested the new update with the same reproduction and the issue still persists.

@s3812497 Yep. #6622 fixed something relatively obvious, but there’s something else going on here. This issue should be reopened.

I dug into this again and am seeing a difference between client and server where I don’t know how to best handle it:

• when you go to /page directly, setting a cookie in its load function, that cookie is scoped to the / path
• when you go to /page/ directly (note the trailing slash; set through trailingSlash: 'always'), setting a cookie in its load function, that cookie is scoped to the /page path
• when you go to the /page through a client-side navigation, setting a cookie in its load function, that cookie is scope to the /page path

Reason for the difference in behavior: it seems that the browser goes back to the last slash and uses that as the path. This means

• direct hit goes to the /page path -> /
• direct hit goes to the /page/ path -> /path
• the client-side navigation calls the page through /page/__data.json -> /path

I’m not sure about the best way forward here.

• add logic to cookie calls to set the path to something specific (basically replicating the browser behavior to avoid the __data.json mismatch)?
• warnings? how exactly?
• set the default path to basePath || '/' after all? FWIW some frameworks also do this, .NET for example https://learn.microsoft.com/en-us/dotnet/api/system.net.cookie.path?view=net-6.0#remarks . PHP / Nuxt3 behave as we do currently

I think I lean towards a combinations of option 1 and 2