Add the ability to edit the domain list

[LIyoai]

Add the ability to edit the domain list to assign a domain to a container.
That way I could fill the list up front with all work domains etc.

┆Issue is synchronized with this Jira Task

[jonathanKingston]

I think this is a duplicate, it certainly has been discussed elsewhere.

[maxnordlund]

I think this is related to #719

[grahamperrin]

Also tiansh/always-in-container#1

[isavcic]

Any news on this? I desperately need this feature to assign an AWS account login page per container, but I can't do it right now because it immediately redirects.

[kurahaupo]

@isavcic

You may need one or both of these:

1. turn off Limit to Designated Sites; and/or
2. 1. edit /etc/hosts and add the hostname of the login page with 127.0.0.1 (or indeed, any 127.nn.nn.nn);
   2. load the login page - it will fail because of the hosts entry;
   3. add it to a container;
   4. remove the entry from etc/hosts.

The additions and removals in /etc/hosts can be done in bulk, of course.

If you're on a system that doesn't have /etc/hosts, there may be an equivalent file, or you may be able to set a deliberately non-working proxy in Firefox, to similar effect; however that will affect all sites while it's in effect, not just the login sites.

My understanding is that automatic transfer between containers is based on matching domains, not whole URLs, which means that you can't assign http://some.site/login?user=foo and http://some.site/login?user=bar to different containers.

[kurahaupo]

An example of the kind of problem encountered by users is #2415.

[xanoni]

Any news on this? I desperately need this feature to assign an AWS account login page per container, but I can't do it right now because it immediately redirects.

Maybe tricking the server into returning a 404 (or similar) helps, see here: #1670 (comment)

EDIT: an improved workaround would be simply disabling redirects temporarily #1670 (comment)