# Conflicting Headers with  Kuberntes and OneAgent

**URL:** <https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102>\
**Category:** Container platforms\
**Tags:** nginx, headers, kubernetes\
**Created:** [September 27, 2019, 1:10pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102 "2019-09-27T13:10:49Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jerome\_cizeron](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@jerome\_cizeron](https://community.dynatrace.com/u/jerome_cizeron)\
**Post date:** [September 27, 2019, 1:10pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/1 "2019-09-27T13:10:49Z")

</div>

We got some issue as DYNATRACE is using ETag hearder to store info which are conflicting with standart Cache managment. Is ther a way to define specific hearder to be use by Dynatrace as for example X-DT-MYHEADER hearder typ

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [September 27, 2019, 1:23pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/2 "2019-09-27T13:23:57Z")

</div>

Are you sure that DT is using ETag? We have multiple kuberneties environments and we’ve never had conflict on such header parameter. If there is such in your example, you should open support ticket. Unfortunately users are not able to define custom header params.

Sebastian

---

<div class="post-metadata">

**Author:** ![jerome\_cizeron](https://avatars.discourse-cdn.com/v4/letter/j/e36b37/32.png) [@jerome\_cizeron](https://community.dynatrace.com/u/jerome_cizeron)\
**Post date:** [September 27, 2019, 2:06pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/3 "2019-09-27T14:06:00Z")

</div>

For me, I get this information for dev team ETag is modified as followed

W/“d2d8037bd06cd0df9fc0aaa1cbb9bf38:dtagent101751909170927224xag:dtagent101751909170927224xag”

On which you can see dtagent, all add data block our caching efficiency.

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [September 27, 2019, 2:29pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/4 "2019-09-27T14:29:37Z")

</div>

Open support ticket then.

Sebastian

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [September 27, 2019, 3:31pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/5 "2019-09-27T15:31:42Z")

</div>

You can turn off the etag header usage in application configuration. Dynatrace adds it’s value to etag to speed up changes in application configuration only. Unless you application configuration in Dynatrace changes,the value added is the same. Thus it won’t break up things. I have only encountered problems when web request service sent empty Etag headers. That is however a bug of the monitored application.

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [September 27, 2019, 3:45pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/6 "2019-09-27T15:45:31Z")

</div>

Ok you’re right, there is such setting:

 ![22014-1569599113841.png](https://global.discourse-cdn.com/dynatrace/original/2X/5/5b2d0eabd893b167034f99f9de150937f8d63f8f.png)

Sebastian

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [September 27, 2019, 3:50pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/7 "2019-09-27T15:50:08Z")

</div>

We had an issue when application was sending Etag header with just a space character. Dynatrace added it’s info and the request was cached but it should not be. The app should not pass the header without a proper value.

---

<div class="post-metadata">

**Author:** ![nicolas\_nguyen](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/nicolas_nguyen/32/28450_2.png) [@nicolas\_nguyen](https://community.dynatrace.com/u/nicolas_nguyen)\
**Post date:** [June 10, 2024, 6:42pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/8 "2024-06-10T18:42:45Z")

</div>

We have the same issue here but the configuration spotted to solve the issue is not available anymore…

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [June 10, 2024, 7:50pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/9 "2024-06-10T19:50:55Z")

</div>

[@nicolas\_nguyen](https://community.dynatrace.com/user/58031)&nbsp;it’s still there:

 ![Julius_Loman_0-1718049006783.png](https://global.discourse-cdn.com/dynatrace/original/2X/0/082bd50d099ffff8888bb586fe27ebba117e8080.png)

---

<div class="post-metadata">

**Author:** ![nicolas\_nguyen](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/nicolas_nguyen/32/28450_2.png) [@nicolas\_nguyen](https://community.dynatrace.com/u/nicolas_nguyen)\
**Post date:** [June 10, 2024, 8:28pm UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/10 "2024-06-10T20:28:11Z")

</div>

Is there a way to disable this setting a the tenant level ?

thanks

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [June 11, 2024, 6:39am UTC](https://community.dynatrace.com/t/conflicting-headers-with-kuberntes-and-oneagent/22102/11 "2024-06-11T06:39:07Z")

</div>

[@nicolas\_nguyen](https://community.dynatrace.com/user/58031)&nbsp;No, at least not by the user. What exact issue are you facing? Unless the etag headers are implemented incorrectly on your application, this does not have any effect.
