3rd party cookies

[socialatm]

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

[jscher2000]

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?

[socialatm]

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.

[jscher2000 · Accepted solution]

I think it means that these are third parties to one another:

• http://example.com
• https://example.com

Maybe this was meant to prevent secure cookies leaking over an insecure connection?