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!

Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

How to best manage the Containers site list - to prevent sites from breaking

  • 2 Antworten
  • 1 hat dieses Problem
  • 5 Aufrufe
  • Letzte Antwort von user4047994

user4047994
user4047994
more options

I am trying to find out if there is a way to manage the "Site List" for a container by either manually adding sites to the list or (even better) using wildcards.

The configuration that I want is to have multiple containers - but have the containers restricted to the Designated Sites Only. The problem that I am having is that OAUTH tends to bounce around my login through multiple hostnames on the same domain - so I do not seem to be able to add every possible host to the Container's site list.

When the "Limit to Designated Sites" setting is turned on (which is what I want - so I avoid accidentally getting my tabs mixed up) these login requests get opened in the default container - which breaks the login process inside the container.

Consider this as an example - with the hostnames made up. I am trying to visit www.mybank.com. Upon loading the home page and entering my credentials, I get redirected to id.mybank.com. From there, I end up getting redirected to onlinebanking.mybank.com.

Now, I can turn off "Limit to Designated Sites" for the first time I login and I can set www.mybank.com and onlinebanking.mybank.com to always open in my preferred container. However, id.mybank.com never stays up long enough for me to capture it because it does an instant redirect back to the desired page........and hopefully the middle redirection never changes hosts but they might.

The simplest solution to this would be to simply add *.mybank.com to my Container's Site List. Is there a way to do that? If there is not currently a way, can there be?

I am trying to find out if there is a way to manage the "Site List" for a container by either manually adding sites to the list or (even better) using wildcards. The configuration that I want is to have multiple containers - but have the containers restricted to the Designated Sites Only. The problem that I am having is that OAUTH tends to bounce around my login through multiple hostnames on the same domain - so I do not seem to be able to add every possible host to the Container's site list. When the "Limit to Designated Sites" setting is turned on (which is what I want - so I avoid accidentally getting my tabs mixed up) these login requests get opened in the default container - which breaks the login process inside the container. Consider this as an example - with the hostnames made up. I am trying to visit www.mybank.com. Upon loading the home page and entering my credentials, I get redirected to id.mybank.com. From there, I end up getting redirected to onlinebanking.mybank.com. Now, I can turn off "Limit to Designated Sites" for the first time I login and I can set www.mybank.com and onlinebanking.mybank.com to always open in my preferred container. However, id.mybank.com never stays up long enough for me to capture it because it does an instant redirect back to the desired page........and hopefully the middle redirection never changes hosts but they might. The simplest solution to this would be to simply add *.mybank.com to my Container's Site List. Is there a way to do that? If there is not currently a way, can there be?

Alle Antworten (2)

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

Doesn't is work if you add the top level domain (mybank.com) to run in a specific container ?

user4047994
user4047994 Fragesteller
more options

If I could add the top level domain and it worked that would be a perfect solution. The problem that I have with that is: 1) The top-site (in my example, mybank.com) immediately redirects to www.mybank.com - so I can't stop that refresh to add the site using the UI 2) The UI does not allow me to directly enter domains

The flow of the particular site I am trying to add is: 1) Go to www.mybank.com 2) Get redirected to login.mybank.com after I submit a username and password 3) Then there is a redirection to oltpx.mybank.com (or some other random name) that does the 2-factor auth 4) End up at secure.mybank.com where I can see what I wanted.

This does work perfectly if I simply add the (www.mybank.com) and allow the container to do it's work.

The problem that I am encountering is that I want to use the "Limit to Designated Sites" option - to ensure I don't accidentally get my containers mixed up. Adding a top-level domain that enables this "Limit to Designated Sites" option would be perfect - because all of these redirects are within the same domain.

I have been trying the containerise extension with *.mybank.com and a default container for everything else. That seems to work - but it is 2 plugins instead of 1 and the settings do not appear to synchronize from the containerise plugin - making managment of multiple systems more difficult.

I wouldn't mind manually editing a config file, sqlite database or some other profile data - if I knew what to do.

Thank you for any help or guidance you might be able to provide.