Why does Opera have cookie problems on some sites?

[elsi15]

elsi15 last edited by

Ever so often, I experience cookie problems while using Opera (version 33.0). For instance I have never been able to open Google calendar - I get a notification saying that there are problems with my cookie settings instead of being able to see the calendar page at all (other Google services like Gmail seem to work fine). But my cookie settings are normal. I have allowed everything. I have to use another browser to look at my Google calendar which is annoying, but I put up with it because I like Opera otherwise.

That is not the only site I have or have had problems with, sometimes it seems pretty random. Just now I visited a site I don't think I had visited before just to look for a cooking recipe and it told me using the site requires cookies to be allowed.

My question is, why does this happen? Is there some known common problem with Opera and cookies? Am I not doing something right?

[lando242]

lando242 last edited by

Its probably specific to you. I've never encountered an issue with Google services at least. What extensions do you have installed?

[elsi15]

elsi15 last edited by

I don't really have that many extensions either. I only use uBlock (an adblocker) but I had this problem with Google calendar and some other sites before I ever even installed that. Thanks for the clarification that it's not a common problem at least.

[blackbird71]

blackbird71 last edited by

Perhaps it involves some kind of browser-agent sniffing at the site that creates an abnormal cookie-set just for Opera browsers or incorrectly analyzes that Opera is Chrome, and thus fails. You mention another browser opens the calendar OK - which browser is that?

[elsi15]

elsi15 last edited by

I usually use Firefox to use the Google calendar, but it works on all the other browsers I have installed on my computer - Chrome and Internet Explorer as well. That's an interesting explanation, I guess it's not something I could do anything about though.

[blackbird71]

blackbird71 last edited by

Part of the confusion factor in cases like this is that most/many websites include somewhat different coding modules for different visiting browsers, and the code paths or modules applied to the browser are based on how the browser has been identified. If the browser is incorrectly identified via its browser agent or if the website's unique code modules for the correctly-identified browser are flawed, then the site may not function properly on that browser. And, of course, there indeed may be a flaw in the browser code-design itself. The problem is in determining the correct cause, and that's never easy. For major sites or browser brands, there is sometimes enough incentive that either the browser designers or site coders will explore and resolve the issues; for lesser-visited sites, adequate incentives are simply not often there and the problem can persist for some time unresolved.

[elsi15]

elsi15 last edited by

Thanks for the explanation, it makes me content to understand why this is happening even though I can't correct the problem.

[joshl]

joshl last edited by

You can ask the websites' people anyway - whether it's Facebook, Google, or whatever.

It'd be useful if other people tell if they experience such problems: you could clarify which exact configuration you have when you do - the browser build and mode (if it's Turbo enabled, blocking extensions, the AV's or other apps' active protection for the browser on, etc.), [other] proxies used, IP type, maybe LAN "filters"? Like that.
Maybe it depends on/triggered by something particular among all that...