Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating a Default rule that results in a site remaining in the current container #165

Open
dmorlitz opened this issue Oct 7, 2021 · 0 comments

Comments

@dmorlitz
Copy link

dmorlitz commented Oct 7, 2021

I would like to recommend a setting that allows a matching site to be opened in the "current container" - whatever that container is.

The situation I am trying to address is using PayPal (or other sites) with online stores that placed in Default containers. I am using a Default container rule of tmp.{domain} for unmatched containers. If I happen to browse to a site that is a store I might get a container named tmp.store If I wanted to use PayPal - or other payment technologies - I can either set a rule that says either:

  1. !*.paypal.com , Paypal
  2. !*.paypal.com , No Container
  3. no rule - resulting in tmp.paypal

In all of these options PayPal will fail to work because it is in a different container than the tmp.store container.

I would like to recommend the ability to add a rule like

  1. !*.paypal.com , {current container}

which would basically mean "take no action to change the container when navigating to PayPal within a container. I believe this would enable this type of site arrangement to work. I do understand that each time you use this configuration you will force a new login to Paypal (because all of the containers would be different) but typically these payment solutions return you to the primary domain you came from, so you will remain in the same container throughout the process.

Is there any way to do this within Containerise currently? If not, could it be added?

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant