03-16-2024 04:55 AM
I'm building a website and currently testing on localhost. Using nodejs.
Could you explain to me how a link to https://localhost/something is blocked from cookie access?
If I just enter the link as /something it works just fine.
It seems like you're looking at the protocol to determine 3 party when you should be looking at base url.
I can add an exception of course to get around it but our users are not going to do that as you know.
Any help or insight is appreciated. Thanks
Solved! Go to Solution.
03-17-2024 08:36 AM
I think it means that these are third parties to one another:
Maybe this was meant to prevent secure cookies leaking over an insecure connection?
03-16-2024 10:22 AM
Yes, 1st party versus 3rd party takes the protocol into consideration. https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#third-party_cookies
Don't other browsers work the same way?
03-16-2024 11:55 AM
So, any link that starts with https:// is considered third party?
I don't get the logic behind that. I agree, it's not just Firefox.
03-17-2024 08:36 AM
I think it means that these are third parties to one another:
Maybe this was meant to prevent secure cookies leaking over an insecure connection?