postman-app-support
                                
                                 postman-app-support copied to clipboard
                                
                                    postman-app-support copied to clipboard
                            
                            
                            
                        Cookies with Secure attribute not included for localhost
Is there an existing issue for this?
- [X] I have searched the existing issues
Describe the Issue
When working with cookies having SameSite=None, browsers per standard requires the Secure attribute to be true in order to even set the cookie. This could potentially harm developer experience since most local dev environments are using insecure http://localhost. Chrome luckily has solved this by simply regarding localhost as "Secure" thus still including Secure cookies for http://localhost
I'm not sure how other browsers are doing it but I would be great if postman could do this as well. Seems like Secure cookies are added for neither localhost or localhost:3000.
Steps To Reproduce
- Open cookie window in request headers tab
- Add SecureCookiePostmanTest=foo; Secure; Path=/; HttpOnly;to localhost
- Do a reqeust towards localhost
- See how cookie is not included in Cookie response tab
Screenshots or Videos
No response
Environment Information
- Operating System: Mac OS 11.4
- Platform Type: Native App
- Postman Version: 8.9.0
Additional Context?
No response
The issue is still there for 9.13.0
Same issue with Version 9.14.7
Related to #4581
Postman for Windows Version 9.18.2 UI Version 9.18.2-ui-220511-0750 Desktop Platform Version 9.16.0 Architecture x64 OS Platform win32 10.0.22000
Same here! Postman v9.23.3 on Windows
same issue with Version 9.22.2 (9.22.2)
same issue with Version 9.20.0-canary
Still an issue Version 9.31.0 (9.31.0)
Still an issue in version 10.0.42 on Mac
Still an issue in version 10.6.0 on Windows
maybe this can help someone, https://stackoverflow.com/questions/74402197/cookie-in-thunder-client-vs-code-extension
for me, set {secure: false} in cookie work.
How is this still a problem.
I have the same issue cookies on localhost not supported