Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

Opera exceptions "syntax" for addresses?

  • Ok, can someone tell me what I'm doing wrong with the exceptions in Opera that they don't seem to work?

    For example, I've added "" and set it to BLOCK and yet "" cookie ALWAYS gets added to the cookies storage anyway. Why is it so? I thought it shouldn't ever appear with such rule in the exceptions, but it does. What gives? I've tried "", but it colors it red like it's an invalid. I don't quite understand what that [.] in front of domain means exactly and help file is not explaining it either. Or does it just mean the "*." is automatically added in front and is thus not necessary to be added by user himself?

  • @rejzor The [*.] part is for including the sub-domains, I guess.

  • Ok, so I'm using it properly. Question now is, why is it not blocking the cookies? I have their domain blocked and yet they always appear in cookies storage... I thought blocking their domain would block the cookies.

  • @rejzor But there are stored cookies associated with the domain? Or it's just listed there without nothing related to it.

  • Why is it even listed if it's BLOCKED? It makes no sense to have there an entry for it, be it empty or not. It's impossible to check whether it's being blocked or not if it's listed there and that's super stupid. I end up having same ridiculous amount of cookies there which is pretty much impossible to manage because there are so many entries, last thing I need is now having to open each and every damn thing and check "if it actually contains anything". If it's blocked, there should be NO entry for it. Also, one of blocked is "" and it has tons of shit in it, a lot of stuff that could be unique user identification strings. And despite being blocked, it keeps getting recreated in cookies storage. I don't get it, if it says BLOCKED it should be that way. BLOCKED. I don't want it there. AT ALL.

  • @rejzor Don't know why but I remember that it always worked this way, even in Opera Presto.

  • But that's utterly stupid. How am I suppose to manage cookies by hand and know which one was blocked and which wasn't if I have to open every single one of entries and check them if they have anything stored. If it's blocked it should NOT exist on the list. Period. If it's cleared on exit, delete it on exit, but list it till that happens. If it's allowed, list it. How is that such a hard concept to understand as a design choice? It's like the very essence of good UX. Otherwise, why have the bloody cookies manager integrated if it's an absolute lobotomy to use it because it's designed so clumsily?

  • Just checked and "Clear on exit" actually deletes them from the list. But having them blocked keeps them on the list. This makes even less sense. It seems to me like th "Block" feature is actually broken and doesn't work as intended. If it's blocked, it shouldn't be listed. Period. This really needs to be fixed.

  • @rejzor Then it needs to be done by Chromium.

    Anyway, if you set it to block all cookies then I guess you may get what you want.

  • Yeah, well I don't want to block ALL cookies. I just want to block select ones. And if you say it has been this way since Presto, it's a bit hard to believe it's a Chromium thing. Besides, Chromium is just a base. They can do anything they want with it. Including this. It's why I'm using Opera in the first place. They have an identity and a will of their own, it's why they make such a good browser (unlike Chrome which is a dumpsterfire from UI and UX perspective).

    Btw, do you happen to know why using "" as block cookie filter doesn't also cover ""? It's a bit annoying adding both of such entries when single "" should cover all subdomains. Unless I'd specify a subdomain in which case it should only cover that one.

  • @rejzor Are you using [*.]

  • Something is wrong with Exclusions. When using "" as rule for Clear on Exit, it works. But same rule doesn't work for BLOCK. But when I add that [*.] in front, it also works for BLOCK. That's absolutely bizarre and unexpected behavior. Why same thing doesn't work for different actions/rules?

  • Ok, this is just absolutely stupid. is back again despite the use of [*.]. This thing just has mind of its own an it's pissing me off. I don't even know if ANY of the rules even actually works. Idiotic.

    Can someone from actual Dev team comment on how to even properly use Exclusions because help doesn't seem to explain anything and what I'm entering in it doesn't seem to work at all or when it feels like it...

  • Can someone tell me how to add BLOCK exception for all cookies that originate from:
    "ad" or "ads" subdmain?

    In most other apps, the syntax is simply "ad." or "ads.". But if I do this in Opera, it just makes the address red, meaning I'm trying to use illegal syntax. I want to globally block all cookies that originate from ad. subdomain so I don't have to manually block every single damn domain by hand. Can this be done? I've checked all documentation of Cookies exceptions manager and there is no info about it what so ever about allowed syntaxes for addresses in it which is ultra annoying...

Log in to reply

Looks like your connection to Opera forums was lost, please wait while we try to reconnect.