# Http-response set-header with condition, not working

**URL:** <https://discourse.haproxy.org/t/http-response-set-header-with-condition-not-working/3108>\
**Category:** Help!\
**Created:** [October 18, 2018, 7:25am UTC](https://discourse.haproxy.org/t/http-response-set-header-with-condition-not-working/3108 "2018-10-18T07:25:27Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Gazelle3574](https://avatars.discourse-cdn.com/v4/letter/g/839c29/32.png) [@Gazelle3574](https://discourse.haproxy.org/u/Gazelle3574)\
**Post date:** [May 2, 2020, 2:02pm UTC](https://discourse.haproxy.org/t/http-response-set-header-with-condition-not-working/3108/6 "2020-05-02T14:02:02Z")

</div>

I am getting the same error in HAProxy, while using it via the OpnSense firewall.

> acl ‘\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*’ will never match because it only involves keywords that are incompatible with ‘frontend http-response header rule’

My case is a bit more weird though, since I try to delete a header :

![haproxy](https://us1.discourse-cdn.com/flex016/uploads/haproxy/original/2X/1/1309289d8e79b9a2b420ff087435abdf6372658a.png)

Your previous explanation of the issue does not apply here, I think.  
Here, we don’t need any data from the request in order to process the response.

Any idea how I can solve this?  
I don’t see OpnSense supporting something related to txn variables and I don’t see how a variable would help in my case.  
There is an option for :

> Specify a HAProxy rule/ACL that is currently not supported by the GUI.

![haproxy1](https://us1.discourse-cdn.com/flex016/uploads/haproxy/original/2X/1/1436d136a4d3cf1cb795871095a1cdfd0ce9ffc7.png)

…but I am not sure what I can do with it.  
I guess I could have pasted the:

> http-request set-var(txn.path) path

…if I was fixing the original poster’s case, hoping that it works, but in my case I see no benefit in doing that.

---

_[View the full topic](https://discourse.haproxy.org/t/http-response-set-header-with-condition-not-working/3108)._