-
Notifications
You must be signed in to change notification settings - Fork 35
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
feature request to have policy set such as acl/intercept to define what traffic goes via ICAP #355
Comments
Yes, you are right.
Yes. It's also my preferred way. |
Do you like it like this (A): icap_reqmod_service:
forward_policy:
default: bypass
child:
forward:
- example.com
- example.org
url: icap://icap.example.com:1344/inspect
icap_respmod_service:
forward_policy:
default: bypass
child:
forward:
- example.com
- example.org
url: icap://icap.example.com:1344/inspect Or like this (B): icap_forward_policy:
default: bypass
child:
forward:
- example.com
- example.org
icap_reqmod_service:
url: icap://icap.example.com:1344/inspect
icap_respmod_service:
url: icap://icap.example.com:1344/inspect We could do the same approach as with the
That is what I currently had in mind, WDYT? I'm also fine if something completely different, would be happy to hear your feedback and pointers either way. |
@GlenDC I would prefer B. The policy however can be set to
|
It's a feature request I'm willing to contribute code for in case code is needed.
Currently it seems that as soon as ICAP is enabled, all applicable traffic goes over it.
I would like however to have the option, akin to what we can do for intercept policies
and ACL rules, to be able to define filters on what traffic actually goes over ICAP.
Could be a new option in the
icap_reqmod_service
/icap_respmod_service
configs? or how do you see that?The text was updated successfully, but these errors were encountered: