# Dynatrace X-dtpc

**URL:** <https://community.dynatrace.com/t/dynatrace-x-dtpc/44861>\
**Category:** Dynatrace API\
**Tags:** dynatrace-managed\
**Created:** [March 26, 2024, 8:53am UTC](https://community.dynatrace.com/t/dynatrace-x-dtpc/44861 "2024-03-26T08:53:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sarathsampath04](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@sarathsampath04](https://community.dynatrace.com/u/sarathsampath04)\
**Post date:** [March 26, 2024, 8:53am UTC](https://community.dynatrace.com/t/dynatrace-x-dtpc/44861/1 "2024-03-26T08:53:16Z")

</div>

Hi,  
X-dtpc header is added only in few api’s and the api’s having x-dtcp header are failing after having it. Any workover to overcome this issue?

---

<div class="post-metadata">

**Author:** ![PacoPorro](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pacoporro/32/36087_2.png) [@PacoPorro](https://community.dynatrace.com/u/PacoPorro)\
**Post date:** [March 26, 2024, 9:13am UTC](https://community.dynatrace.com/t/dynatrace-x-dtpc/44861/2 "2024-03-26T09:13:17Z")

</div>

x-dtcp is used for correlation of cross-origin XHRs

You should consider disabling RUM at the process group level for the related api process.

> **[Control RUM Classic at the process group level](https://docs.dynatrace.com/docs/observe/digital-experience/rum-classic/web-applications/additional-configuration/rum-for-process-groups)**
>
> Learn how to control RUM Classic at the process group level.

---

<div class="post-metadata">

**Author:** ![simon\_schatka](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@simon\_schatka](https://community.dynatrace.com/u/simon_schatka)\
**Post date:** [March 26, 2024, 9:24am UTC](https://community.dynatrace.com/t/dynatrace-x-dtpc/44861/3 "2024-03-26T09:24:18Z")

</div>

Can you clarify which header you are talking about?

There is no x-dtcp header.

- There is a x-dtc header (which is what&nbsp;[@PacoPorro](https://community.dynatrace.com/user/40713)&nbsp;is referring to)
- anda x-dtpc header.

If you mean the x-dtc header:

There is a documentation on how to configure it:&nbsp;[Link cross-origin XHR user actions and their distributed traces in RUM Classic — Dynatrace Docs](https://docs.dynatrace.com/docs/platform-modules/digital-experience/web-applications/initial-setup/link-cross-origin-xhrs)

Basically you configure yourself on which API calls this header is added and you have to take care yourself that this header is accepted, by setting the&nbsp;Access-Control-Allow-Headers: x-dtc header. (how that is done, depends on how your application works, so we can’t give any guidance there)

If it is the x-dtpc header you are talking about:

- Ideally you change your application to accept that header
- You can disable this header by adding the custom configuration property “dpch=1” to your application. This WILL affect the accurracy of the correlation!

Both headers are set by the RUM Javascript code, so disabling RUM at process group level will not change anything.

---

<div class="post-metadata">

**Author:** ![PacoPorro](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pacoporro/32/36087_2.png) [@PacoPorro](https://community.dynatrace.com/u/PacoPorro)\
**Post date:** [March 26, 2024, 9:29am UTC](https://community.dynatrace.com/t/dynatrace-x-dtpc/44861/4 "2024-03-26T09:29:39Z")

</div>

My fault x-dtpc:&nbsp;Identifies proper endpoints for beacon transmission; includes session ID for correlation

> **[Infrastructure pass-through requirements for RUM Classic](https://docs.dynatrace.com/docs/observe/digital-experience/rum-classic/web-applications/initial-setup/infrastructure-pass-through-requirements-classic)**
>
> Learn which requests, headers, and cookies must pass through your infrastructure for RUM Classic to work as expected.

---

<div class="post-metadata">

**Author:** ![sarathsampath04](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@sarathsampath04](https://community.dynatrace.com/u/sarathsampath04)\
**Post date:** [March 26, 2024, 10:32am UTC](https://community.dynatrace.com/t/dynatrace-x-dtpc/44861/5 "2024-03-26T10:32:47Z")

</div>

Where can I set the custom property&nbsp;“dpch=1”?  
In the api application or is there any way to do configuration in dynatrace ?

---

<div class="post-metadata">

**Author:** ![simon\_schatka](https://avatars.discourse-cdn.com/v4/letter/s/779978/32.png) [@simon\_schatka](https://community.dynatrace.com/u/simon_schatka)\
**Post date:** [March 26, 2024, 11:28am UTC](https://community.dynatrace.com/t/dynatrace-x-dtpc/44861/6 "2024-03-26T11:28:56Z")

</div>

Go to your RUM Application settings (open application and click “edit”), then on the left side expand “Capturing” and select “custom configuration properties”

---

<div class="post-metadata">

**Author:** ![Vigneshwar](https://avatars.discourse-cdn.com/v4/letter/v/9dc877/32.png) [@Vigneshwar](https://community.dynatrace.com/u/Vigneshwar)\
**Post date:** [March 29, 2024, 6:21am UTC](https://community.dynatrace.com/t/dynatrace-x-dtpc/44861/7 "2024-03-29T06:21:45Z")

</div>

Setting dpch=1 in dynatrace settings does solve this issue, but we are getting another header named x-dtreferer causing this same cors issue now.
