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

allow wildcard subdomain whitelisting from menu when using stricter classification policies #9

Closed
msxfm opened this issue Jul 7, 2014 · 2 comments

Comments

@msxfm
Copy link

msxfm commented Jul 7, 2014

Issue by jsamuel
Thursday Dec 22, 2011 at 18:45 GMT
Originally opened as RequestPolicy/requestpolicy#9


imported trac ticket
created: 2009-06-21 17:16:17
reporter: justin

When using stricter classification policies, there are times when users want to whitelist all subdomains of the current domain. After #8 has been completed, displaying menu items for wildcard subdomain whitelisting should either be enabled by default or should be an optional preference when using stricter classification policies.

@msxfm
Copy link
Author

msxfm commented Jul 7, 2014

Comment by jsamuel
Thursday Dec 22, 2011 at 18:45 GMT


imported trac comment
created: 2009-12-16 09:41:14
author: NukePower

See also #63

@myrdd
Copy link
Member

myrdd commented Oct 16, 2016

displaying menu items for wildcard subdomain whitelisting should either be enabled by default or should be an optional preference when using stricter classification policies.

Wildcards are already implemented in v1.0. – Menu items like *.site.com -> *.site.com are available, apart from the *.site.com -> subdomain.site.com rules. Closing.

@myrdd myrdd closed this as completed Oct 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants