We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
client IDs in clientGroupsBlock configuration block are matched case-sensitive now. Example:
$ host 192.168.1.1 1.1.168.192.in-addr.arpa domain name pointer UpperCase.test.local $ cat config.yaml ... blocking: clientGroupsBlock: UpperCase.test.local: [ads] # this matches uppercase.test.local: [ads] # this doesn't match
DNS is by specs case-insensitive and thus Client ID match from PTR should be case-insensitive.
Thanks.
The text was updated successfully, but these errors were encountered:
feat: client name in clientGroupsBlock should not be case-sensitive (#…
b079d27
…894)
120e32c
…894) (#913)
Successfully merging a pull request may close this issue.
client IDs in clientGroupsBlock configuration block are matched case-sensitive now. Example:
DNS is by specs case-insensitive and thus Client ID match from PTR should be case-insensitive.
Thanks.
The text was updated successfully, but these errors were encountered: