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!

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Enable pop-up for site with multiple pages/servers - wildcards or regex?

  • 5 respostas
  • 1 tem este problema
  • 8 visualizações
  • Última resposta de Nuke

more options

I've found a number of sites that have numerous pages or servers that I can't enable the pop-up to work properly.

For example the site will have:

https://www5.site.com https://www.site.com https://www3.site.com

I can't tell which site will be pushing the pop-up so setting the above into the "enable pop-up" still doesn't allow the pop-up to happen.

I don't want to blanket enable all sites but rather use a regex or some wildcards to allow *.site.com to push pop-ups.

I've tried to use wildcards but the dialog box gives an error that I've entered an invalid website address.

How can I use wildcards to allow pop-ups from websites with multiple pages?

Thanks.

I've found a number of sites that have numerous pages or servers that I can't enable the pop-up to work properly. For example the site will have: https://www5.site.com https://www.site.com https://www3.site.com I can't tell which site will be pushing the pop-up so setting the above into the "enable pop-up" still doesn't allow the pop-up to happen. I don't want to blanket enable all sites but rather use a regex or some wildcards to allow *.site.com to push pop-ups. I've tried to use wildcards but the dialog box gives an error that I've entered an invalid website address. How can I use wildcards to allow pop-ups from websites with multiple pages? Thanks.

Solução escolhida

I'm not sure why Firefox would create the exception for the www. prefixed domain in your case as I'm seeing exceptions for http://site.com and https://site.com

Try to include the protocol and create the exception for https://site.com

Ler esta resposta 👍 0

Todas as respostas (5)

more options

You need an exception for the site.com top level domain to include subdomains. Firefox creates two exceptions, one for HTTP and one for HTTPS.

more options

Thank you @cor-el for your suggestion. I can't get this to work.

When I try to add site.com in the exception, it automatically creates http://www.site.com and https://www.site.com. This what I think you have suggested.

But that will not allow the pop-ups from https://www5.site.com. The https://www5.site.com pop-up is blocked even though it is part of site.com.

The exception should allow all related pages on site.com (including www5.site.com; www3.site.com, etc.) without having to add each of the multiple sites manually.

Alterado por Nuke em

more options

Thank you @cor-el for your suggestion. I can't get this to work.

When I try to add site.com in the exception, it automatically creates http://www.site.com and https://www.site.com. This what I think you have suggested.

But that will not allow the pop-ups from https://www5.site.com. The https://www5.site.com pop-up is blocked even though it is part of site.com.

The exception should allow all related pages on site.com (including www5.site.com; www3.site.com, etc.) without having to add each of the multiple sites manually.

more options

Solução escolhida

I'm not sure why Firefox would create the exception for the www. prefixed domain in your case as I'm seeing exceptions for http://site.com and https://site.com

Try to include the protocol and create the exception for https://site.com

more options

Thank you @cor-el. I added only site.com and it worked creating http://site.com and https://site.com. When I accessed the site.com and it sent me to www5.site.com, FF popped the message "Firefox blocked ..." but then went to the https://www5.site.com. So it appears that the wildcard is assumed and does work even if it momentarily hangs. Thanks for your help!