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

Is it possbile to add an option/param to enable the time range control for the Hosts Blocklists #4746

Closed
2 tasks
GreatMichaelLee opened this issue Jul 16, 2022 · 1 comment
Labels
duplicate Duplicate or merged issues.

Comments

@GreatMichaelLee
Copy link

GreatMichaelLee commented Jul 16, 2022

Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • [x ] I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

Problem Description

It is incovinence that there is no time range control(allow/deny) for the host blocklists, so if once I enable it ,it will be applied all day until if I disable or remove it. In some case, I have to enable/disable those rules by day or night situation and seems for now there is no way to implement this. (if there is, please let me know).

Proposed Solution

If it is possilbe that to implement an addition parameter to be parsed that which can control this custom filtering rules enable/disable regarding to the configured time range? like this
||google.com^$time='22:00-07:00' --> by default it is all day, and if configured, then only the specified time is effective.

Alternatives Considered

if it is possible that I can private define the "blocked service" to implement this is also ok.

Additional Information

NA

@ainar-g
Copy link
Contributor

ainar-g commented Aug 24, 2022

Duplicate of #1203 and many other similar issues. This is should at least partially be implemented in the v0.108 cycle.

@ainar-g ainar-g closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2022
@ainar-g ainar-g added duplicate Duplicate or merged issues. and removed feature request labels Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate or merged issues.
Projects
None yet
Development

No branches or pull requests

3 participants