vite can not get cookie from set-cookie

[fishermess]

Describe the bug

When I send /api/login request to server, it sends me Set-cookie, but I can get cookie in browser.I tried change proxy '/api' to '/', it is useful in vue-cli, however it doesn't send to server any more rather than visit local static resources.

Reproduction

https://gitee.com/kooji/vue3-demo

Steps to reproduce

1. problem 1
   set proxy
   '/': {
   target: env.VITE_BASE_URL,
   secure: false,
   headers: {
   Connection: 'keep-alive',
   },
   changeOrigin: true,
   rewrite: (path: string) => path.replace(/^/api/, ''),
   },
   can not send request and get local static resources.

2.problem 2
set proxy
'/a': {
target: env.VITE_BASE_URL,
secure: false,
headers: {
Connection: 'keep-alive',
},
changeOrigin: true,
rewrite: (path: string) => path.replace(/^/api/, ''),
},
or
'/ap': {
target: env.VITE_BASE_URL,
secure: false,
headers: {
Connection: 'keep-alive',
},
changeOrigin: true,
rewrite: (path: string) => path.replace(/^/api/, ''),
},
When i send /api/login it should not send successfully but it did.

3.problem 3
I have to set proxy as
'/api': {
target: env.VITE_BASE_URL,
secure: false,
headers: {
Connection: 'keep-alive',
},
changeOrigin: true,
rewrite: (path: string) => path.replace(/^/api/, ''),
},

It works, but it cannot get Set-cookie from server.Because cookie path has been setted as '/api'.

System Info

No info, just doesn't work when proxy setted '/', can not send request and get local static resources.

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

1. problem 1
   can not send request and get local static resources.

This is expected. You are proxying all paths so the request doesn't hit Vite's internal middlewares.

2. problem 2
   When i send /api/login it should not send successfully but it did.

This is also expected. It's a prefix match.

3. problem 3
   It works, but it cannot get Set-cookie from server.Because cookie path has been setted as '/api'.

AFAIK Vite doesn't change Set-Cookie header as long as cookiePathRewrite is not set. I guess the server behind the proxy sets the cookie with path.

[fishermess]

1. problem 1
   can not send request and get local static resources.

This is expected. You are proxying all paths so the request doesn't hit Vite's internal middlewares.

2. problem 2
   When i send /api/login it should not send successfully but it did.

This is also expected. It's a prefix match.

3. problem 3
   It works, but it cannot get Set-cookie from server.Because cookie path has been setted as '/api'.

AFAIK Vite doesn't change Set-Cookie header as long as cookiePathRewrite is not set. I guess the server behind the proxy sets the cookie with path.

1.The write way of problem1 is works in vue-Cli.
2.Why does vite choose prefix match rather than equal?
3.The server send set-cookie without path, and I think it is too unconvinent without rewritecookie interface for vite developers.

[sapphi-red]

1.The write way of problem1 is works in vue-Cli.

Vite does not aim for one-to-one compatibility with Vue CLI. This behavior has been existed for a long time and IMHO not worth making a breaking change unless there's many advantages.

2.Why does vite choose prefix match rather than equal?

It is common to proxy all paths under a specific path and most of the case that way works with people that want to proxy a single path.

3.The server send set-cookie without path, and I think it is too unconvinent without rewritecookie interface for vite developers.

I don't get what you mean. cookiePathRewrite option does exist in Vite. If you set that option, you can rewrite the path of the Set-Cookie header. If you don't set that option, then Vite will pass the header as-is. If your server behind the proxy sends Set-Cookie without a path and you don't set cookiePathRewrite, then the header won't include a path.

[fishermess]

3.The server send set-cookie without path, and I think it is too unconvinent without rewritecookie interface for vite developers.

I don't get what you mean. cookiePathRewrite option does exist in Vite. If you set that option, you can rewrite the path of the Set-Cookie header. If you don't set that option, then Vite will pass the header as-is. If your server behind the proxy sends Set-Cookie without a path and you don't set cookiePathRewrite, then the header won't include a path.

This method I tried, but it doesn't work for me, because the set-cookie of response don't set path.
cookiePathRewrite: {
'': '/',
}, or cookiePathRewrite: {
'*': '/',
},
doesn't work.

[fishermess]

2.Why does vite choose prefix match rather than equal?

It is common to proxy all paths under a specific path and most of the case that way works with people that want to proxy a single path.

I can't see eye to eye with you to this design. if I set proxy '/a', it works on ‘/a/login’, it is OK.However it can also works on '/api/login'.It is not reasonable.