26 Mar 2024 08:53 AM - edited 26 Mar 2024 10:38 AM
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?
Solved! Go to Solution.
26 Mar 2024 09:13 AM - edited 26 Mar 2024 09:13 AM
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.
https://docs.dynatrace.com/docs/shortlink/rum-for-process-groups
26 Mar 2024 09:24 AM - edited 26 Mar 2024 09:25 AM
Can you clarify which header you are talking about?
There is no x-dtcp header.
If you mean the x-dtc header:
There is a documentation on how to configure it: https://docs.dynatrace.com/docs/platform-modules/digital-experience/web-applications/initial-setup/l...
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 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:
Both headers are set by the RUM Javascript code, so disabling RUM at process group level will not change anything.
26 Mar 2024 09:29 AM
My fault x-dtpc: Identifies proper endpoints for beacon transmission; includes session ID for correlation
https://docs.dynatrace.com/docs/shortlink/rum-firewall#request-headers
26 Mar 2024 10:32 AM - edited 26 Mar 2024 10:35 AM
Where can I set the custom property "dpch=1"?
In the api application or is there any way to do configuration in dynatrace ?
26 Mar 2024 11:28 AM
Go to your RUM Application settings (open application and click "edit"), then on the left side expand "Capturing" and select "custom configuration properties"
29 Mar 2024 06:21 AM
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.