Cookies and Iframes

Sounds Familiar? It happened to me some time ago and it took some digging around to understand and diagnose the problem. This kind of scenario used to work without problems but now, with modern browsers, you need to do a couple of things to make your iframed stuff work properly.

When I bump into this kind of problem I usually appreciate finding a post that offers a solution as fast as possible so here it goes:

You need to set your cookie with the attributeSameSite=None and also including the attribute Secure.

Now, with the problem already solved, we can use a couple of minutes to understand what we have just done.

Cookies that match the domain of the current site are referred to as first-party cookies. Cookies from domains other than the current site are referred to as third-party cookies.

For a long time, both kinds of cookies were treated equally: every time you request an URL all the cookies for that URL were sent with the request. There are a variety of problems associated with this behavior:

Related posts:

When talking about sex in religion, it is considered to be taboo. Something that should never be discussed about and is forbidden. When coming to college perspectives change. When talking about sex…

Just type the word and get the most common meaning with this simple web app.

In 2016 we set ourselves the exciting but daunting challenge of merging two teams with different processes, approaches and ways of communicating. Rather than just choose one team’s methodology and…