27 Sep 2019 02:10 PM - last edited on 15 Dec 2021 02:17 PM by MaciejNeumann
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
Solved! Go to Solution.
27 Sep 2019 02:23 PM
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
27 Sep 2019 03:06 PM
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.
27 Sep 2019 03:29 PM
Open support ticket then.
Sebastian
27 Sep 2019 04:31 PM
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.
27 Sep 2019 04:45 PM
Ok you're right, there is such setting:
Sebastian
27 Sep 2019 04:50 PM
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.
10 Jun 2024 07:42 PM
We have the same issue here but the configuration spotted to solve the issue is not available anymore...
10 Jun 2024 08:50 PM
@nicolas_nguyen it's still there:
10 Jun 2024 09:28 PM
Is there a way to disable this setting a the tenant level ?
thanks
11 Jun 2024 07:39 AM
@nicolas_nguyen 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.