Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Firefox Multi-Account Containers | Is it possible to "limit to designated" no matter what is the subdomain?

  • 2 отговора
  • 0 имат този проблем
  • Последен отговор от tomerva22+2nd5wg4l

more options

When I'm using Firefox Multi-Account Containers with the option "Limit to designated sites" enabled, I encounter an annoying issue when navigating between different subdomains of the same website.

For example, if you navigate from "https://www.google.com" to "https://accounts.google.com," you will exit the "Google" container until that subdomain is manually added to the container.

I thought it would be nice if I could somehow create a container for "https://*.google.com/" (where * acts as a wildcard, as explained in the note below).

  • Is it possible to do this? If so, how, and what is the safest way? (See note below)
  • If not, is there any viable solution to this problem?

Note: The RegEx (or wildcard) * should only allow alphanumeric variations to prevent security vulnerabilities. For instance, "https://www.PhishingSite.com/WeStealYourAccount.google.com" could bypass the container if * is not restricted properly. In this case, * could mistakenly refer to "www.PhishingSite.com/WeStealYourAccount"

Thank you for your help

When I'm using Firefox Multi-Account Containers with the option "Limit to designated sites" enabled, I encounter an annoying issue when navigating between different subdomains of the same website. For example, if you navigate from "https://www.google.com" to "https://accounts.google.com," you will exit the "Google" container until that subdomain is manually added to the container. I thought it would be nice if I could somehow create a container for "https://*.google.com/" (where * acts as a wildcard, as explained in the note below). * Is it possible to do this? If so, how, and what is the safest way? (See note below) * If not, is there any viable solution to this problem? Note: The RegEx (or wildcard) * should only allow alphanumeric variations to prevent security vulnerabilities. For instance, "https://www.PhishingSite.com/WeStealYourAccount.google.com" could bypass the container if * is not restricted properly. In this case, * could mistakenly refer to "www.PhishingSite.com/WeStealYourAccount" Thank you for your help

Всички отговори (3)

more options

Neat idea! I think you may have better luck posting this suggestion on GitHub.

Hope that helps -- Ed

Полезно?

more options

Edward Sullivan said

Neat idea! I think you may have better luck posting this suggestion on GitHub. Hope that helps -- Ed

Sure thing,

I posted it here: Idea suggestion on GitHub

Thanks!

Променено на от tomerva22+2nd5wg4l

Полезно?

more options

Edward Sullivan said

Neat idea! I think you may have better luck posting this suggestion on GitHub. Hope that helps -- Ed

Sure thing,

I submitted an Idea suggestion on GitHub

Thanks!

Полезно?

Задаване на въпрос

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.