**What happened**:

According to the tag controller-1.10.1 the file nginx.tmpl should support the Custom-Headers functionality implemented in #9742. But it does not.

Link to nginx.tmpl in tag controller-1.10.1: https://github.com/kubernetes/ingress-nginx/blob/controller-v1.10.1/rootfs/etc/nginx/template/nginx.tmpl

When comparing with the release-1.10 branch I see that the support is not included there: https://github.com/kubernetes/ingress-nginx/blob/release-1.10/rootfs/etc/nginx/template/nginx.tmpl

Therefore it seems either the tagging process was not working correctly (i.e. tagged based on main) or branch release-1.10 was not updated and was then used as base for the image build process.

**What you expected to happen**:

I expect that I am able to set custom headers. But as the function is not available in the file nginx.tmpl it basically can't work at all.

**NGINX Ingress controller version** (exec into the pod and run nginx-ingress-controller --version.):

1.10.1

**Kubernetes version** (use `kubectl version`):

1.28.6

**Environment**:

does not matter in that case, I believe.

**How to reproduce this issue**:

Add `global-allowed-response-headers: Content-Type,X-no-meaning` to the config map of the ingress controller.

Add an annotation `nginx.ingress.kubernetes.io/custom-headers: custom-headers-configmap` to an ingress.

Create said configmap in the same namespace (using `Content-Type: text/json` as data).

Test if the header has changed from text/html to text/json.

**Anything else we need to know**:

I believe the error happened while tagging controller-1.10.1 as it seems to be based of main instead of branch release-1.10.
The release notes of the controller (https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.10.1) also do not reference #9742.

Maybe all this only happened because the documentation https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#custom-headers already contains an annotation that will only be present with the next minor release 1.11.0. But I really don't know.

<!-- 
/kind documentation
/remove-kind bug
-->

Custom-Headers annotation not working with 1.10.1 (changes are visible in git tag for 1.10.1)
This is a GitHub Issue
repo:ingress-nginx
owner:kubernetes
Title : Custom-Headers annotation not working with 1.10.1 (changes are visible in git tag for 1.10.1)
Issue date:

--- start body ---
**What happened**:

According to the tag controller-1.10.1 the file nginx.tmpl should support the Custom-Headers functionality implemented in #9742. But it does not.

Link to nginx.tmpl in tag controller-1.10.1: https://github.com/kubernetes/ingress-nginx/blob/controller-v1.10.1/rootfs/etc/nginx/template/nginx.tmpl

When comparing with the release-1.10 branch I see that the support is not included there: https://github.com/kubernetes/ingress-nginx/blob/release-1.10/rootfs/etc/nginx/template/nginx.tmpl

Therefore it seems either the tagging process was not working correctly (i.e. tagged based on main) or branch release-1.10 was not updated and was then used as base for the image build process.

**What you expected to happen**:

I expect that I am able to set custom headers. But as the function is not available in the file nginx.tmpl it basically can't work at all.

**NGINX Ingress controller version** (exec into the pod and run nginx-ingress-controller --version.):

1.10.1

**Kubernetes version** (use `kubectl version`):

1.28.6

**Environment**:

does not matter in that case, I believe.

**How to reproduce this issue**:

Add `global-allowed-response-headers: Content-Type,X-no-meaning` to the config map of the ingress controller.

Add an annotation `nginx.ingress.kubernetes.io/custom-headers: custom-headers-configmap` to an ingress.

Create said configmap in the same namespace (using `Content-Type: text/json` as data).

Test if the header has changed from text/html to text/json.

**Anything else we need to know**:

I believe the error happened while tagging controller-1.10.1 as it seems to be based of main instead of branch release-1.10.
The release notes of the controller (https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.10.1) also do not reference #9742.

Maybe all this only happened because the documentation https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#custom-headers already contains an annotation that will only be present with the next minor release 1.11.0. But I really don't know.

<!-- 
/kind documentation
/remove-kind bug
-->

--- end body ---

None