为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 5 个回答
  • 1 人有此问题
  • 8 次查看
  • 最后回复者为 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.

被采纳的解决方案

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

定位到答案原位置 👍 0

所有回复 (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.

由Nuke于修改

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

选择的解决方案

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!