Google Chrome warning about Cloudflare cookie

@sandro Who are you? My message was telling @Matteo that nobody needs his condescending judgment after he said to me “I don’t feel the need for being so overly dramatic over something that is in the not near future.”. Everyone in this thread realizes that this is a very real technical issue that Cloudflare support even confirmed to me privately they are working on solving.

You are the one who is rude, by defending your buddies instead of honoring legitimate and paying customers.

Or not – keep doing what you’re doing! I have contacted Cloudflare about you with screenshots before you delete this and other’s messages again.

1 Like

Contact whomever you want :roll_eyes:

I did not even address your issue and I dont really care either to be honest. What I do care about though is a civilised and respectful tone here on the community and you clearly failed in this context. Let alone your posting buddy.

I did not delete a single of your messages, but as you seem to refer to the unrelated and trolling messages I moved to a separate thread (not even those were deleted), you seem to want to associate with that person and his behaviour. I am not sure what kind of light that is supposed to cast on you though.

Thanks @user8963. Fanboys galore indeed! Not to worry though: if this issue isn’t solved in a week, we and MANY OTHERS are leaving Cloudflare (just at the time of their IPO) – it ain’t the only shop in town.

1 Like

(post withdrawn by author, will be automatically deleted in 1 hour unless flagged)

1 Like

@david33 two weeks ago after my reply to you, I addressed this with the Cloudflare staff that can handle this topic. I was told that Cloudflare is addressing it.

It feels like a simple solution, but I believe it needs to go through security scrutiny and engineering implementation.


Is this issue indeed being worked on internally, @cloonan? ETA?

Engineering-wise, there is a little bit of non-trivial code to write to support incompatible browsers, so I can empathize with Cloudflare taking some time to get it right.

However, this is now affecting users of the beta version of the most popular web browser. Developers are especially impacted, and our company is seeing it firsthand with hundreds of developers that use our mission-critical Cloudflare Workers endpoints.


Yes, it is.


Is this being prioritized? Getting these warnings on a very basic website.

Are there any updates on a timeframe for a resolution?

We’ve said multiple times how critical this issue is. In early 2020 when Google flips the switch on Chrome, it can blow up millions of websites (e.g. Intercom’s customers’ websites).

Cloudflare support initially said they will fix it by early December, and now they just said “we don’t have an ETA”.

This is how Cloudflare treats their paying customers.

No longer.

We just closed our paid plans.

We are moving elsewhere, probably AWS.

1 Like

@cloonan can you please provide insight into why this isn’t resolved yet?

50% of Chrome beta users are experiencing broken pages/resources/applications due to rejected Cloudflare cookies. We’re longtime customers of Cloudflare’s Business plan, and this is especially impacting our third party developers and bottom lines. The lack of appropriate action and transparency on this major issue isn’t the Cloudflare I know.

1 Like

I’ve asked for an update from the team and will share it as soon as received.