Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Pop-up Blocker Wildcard

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by cor-el

aacrabtree
aacrabtree
more options

Does anyone know how to use an ACTUAL wildcard in the pop-up blocker whitelist? Everything I find online just says to use the domain and it will allow everything from that domain, but that doesn't work in my experience. My work uses a Citrix client so I can log in from home, and the URL changes depending on what servers are available at the time. It's a massive company, so they have dozens of servers, and it would take me forever to try and whitelist them all.

The URLs are structured as https://server-aa11.login.company.com. So I need to be able to whitelist everything from login.company.com. In Chrome, I do this using [*.]login.company.com and I have no problems with it, but I have been trying to use FF instead of Chrome recently as Chrome has been having problems for me on Windows 11.

Anyone have any advice?

Does anyone know how to use an ACTUAL wildcard in the pop-up blocker whitelist? Everything I find online just says to use the domain and it will allow everything from that domain, but that doesn't work in my experience. My work uses a Citrix client so I can log in from home, and the URL changes depending on what servers are available at the time. It's a massive company, so they have dozens of servers, and it would take me forever to try and whitelist them all. The URLs are structured as https://server-aa11.login.company.com. So I need to be able to whitelist everything from login.company.com. In Chrome, I do this using [*.]login.company.com and I have no problems with it, but I have been trying to use FF instead of Chrome recently as Chrome has been having problems for me on Windows 11. Anyone have any advice?

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You normally create the exception for the "https://login.company.com" top level domain to include possible subdomains.

See also: