-
Notifications
You must be signed in to change notification settings - Fork 14
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
Allow per-domain proxies to be configured with wildcards #232
Comments
After thinking about it, the plan is to have a wildcard by default, when you add though the popup for the current website. Do you think that makes sense? |
If this then a very obnoxious warning should be shown to the user before they are allowed to save a new entry. |
In the v0.9.3 beta, wildcards still get proxied even when setting it to never do so. It's also a bit difficult to find this option, as you would assume the arrow that reveals it is associated with the locations to select since it's right next to it. Furthermore, the domain specified gets wiped before finalizing a location to proxy it to. So if you ever back out from selecting a location due to mistyping it or wanting to never proxy it instead, you'd have to retype it entirely. |
Wildcard is not yet supported. To give you an example, if you setup a proxy Regarding the difficulty about finding the "never proxy" option, where would you expect it to appear? |
I opened as separate issue (#255) for your other feedback. |
For example, if I set up my connection to
*.example.com
to usebg-sof-wg-101
, I wantmaps.example.com
,login.example.com
, andpayments.example.com
to usebg-sof-wg-101
as well.The text was updated successfully, but these errors were encountered: