It is, by using the base
That’s helpful, thanks.
Here is a specific example, that base doesn’t solve (but only benefits from AND in acls a little):
We have a MATCH_allow-iframed ACL that has a whitelist of paths that are allowed to be iframed, and then the following rules:
http-response del-header X-Frame-Options
http-response set-header X-Frame-Options SAMEORIGIN if !MATCH_allow-iframed
But then we wanted to add rules that set X-Frame-Options for a certain path only if it doesn’t come from a certain referrer. In this case it is a single action that uses the ACL, so we could write something like:
http-response set-header X-Frame-Options SAMEORIGIN unless MATCH_allow-iframed or MATCH_path1 MATCH_referer1 or MATCH_path2 MATCH_referer2 or ...
But that leads to a very long condition. We eventually found a better solution, but it made me wonder if there was a better way to do something like that, and if not, why not.