Pete Freitag Pete Freitag

Sessions don't work in Chrome but do in IE

Published on February 06, 2019
By Pete Freitag

I observed an interesting thing today while helping a client. The problem was presented as:

We have a bunch of Chrome users having issues where a session variable is not working between page requests. We set the variable on one page, it is not defined on the next page request. If we tell them to try another browser, such as IE or Edge it works fine.

I have seen problems like this for many years and it doesn't often end up being a difference in the browser implementation, but rather the difference is that the user has essentially cleared their cookies when they try another browser. In this case the client confirmed that the problem went away when they use a new Incognito Chrome browser window.

Attacking the problem

Next I fired open Chrome developer tools to see what was happening. This particular website was serving requests over both http (port 80) and https (port 443). The session cookie (JSESSIONID in this case) was getting the secure flag set when the request came over https, a request over http would not get the secure flag set.

When the secure flag is set by a cookie the browser must not send that cookie over an insecure transport like plain http. This is the essence of what a secure cookie does.


Even though a request over http would cause Tomcat or ColdFusion to set a new JSESSIONID cookie, Chrome will not store that cookie if it already has a cookie with the same name and the secure flag is set.

So here is what happened:

  1. User requests https page, sets JSESSIONID with secure flag.
  2. User makes request to non-secure http page, the JSESSIONID is not sent because it is a secure cookie. The server creates a new session, and tries to set a new JSESSIONID cookie, but the browser ignores this new cookie because it already has a JSESSIONID.
  3. User navigates to another page over non-secure http they do not have a session cookie to pass, repeat step 2.

Do all browsers work this way?

Both Chrome 71, and Firefox 64 prevent a secure cookie from being overwritten on plain http. I tested Edge 42 and it does not work the same way, it will overwrite the secure cookie with the non-secure cookie. Safari 12 works similar to Edge.

My assumption was that the browser would maintain separate cookie values for the secure origin and the non-secure origin in this case. My assumption was not correct on any modern browser. I tested a few old versions of Chrome and found that this implementation was added somewhere between Chrome 37 and Chrome 60 (I didn't want to test each version, I will leave that as an exercise for the reader ;-).

Here's an easy way to test a browser using a site/api for testing HTTP clients, it is useful because it serves requests over both plain http and https. Additionally their set cookie feature will set a cookie with a secure flag when requested over https:

If you see test_secure=2 over http then the browser is overwriting the secure cookie, otherwise you will not see the test_secure cookie over http.

How do you work around this?

Fixing this is pretty straight forward, you have to redirect all http traffic to https and the problem is solved. There is not really any valid use cases for serving content on both http and https that I am aware of.

session cookie chrome ie firefox

Sessions don't work in Chrome but do in IE was first published on February 06, 2019.

If you like reading about session, cookie, chrome, ie, or firefox then you might also like:

Discuss / Follow me on Twitter ↯


Thank you, I was super puzzled by this issue for a very long time (over a year). I finally discovered the same and began searching online for solutions and found your page.
by Vaibhav Garg on 03/05/2020 at 12:47:58 PM UTC
Hi Pete,

Thank you for sharing your findings here. This solved the issue for me where I was getting "this set-cookie was blocked because it was not sent over a secure connection and would have overwritten a cookie with the Secure attribute." when trying to load cookie over http localhost, due to cookies were previously served over https localhost. Once I deleted cookies from https localhost, the cookies were loaded correctly over http localhost again.

Landed from

Freddy from Ottawa, ON.
by freddy on 10/02/2020 at 2:29:47 AM UTC