Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

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

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

Všetky odpovede (3)

more options

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

Hope that helps -- Ed

Pomohla vám táto odpoveď?

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!

Upravil(a) tomerva22+2nd5wg4l dňa

Pomohla vám táto odpoveď?

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!

Pomohla vám táto odpoveď?

Položiť otázku

Ak chcete odpovedať na príspevky, musíte sa prihlásiť do svojho účtu. Ak ešte nemáte účet, položte novú otázku.