RUM dtSa cookie > 4096 bytes ?

[AntonioSousa]

The Dynatrace dtSa RUM cookie encodes the <URL-encoded action name>:
https://www.dynatrace.com/support/help/how-to-use-dynatrace/data-privacy-and-security/data-privacy/c...

An URL can be longer than 4096 bytes, or even much longer. RFCs stipulate that user-agents should support cookies that are at least 4096 bytes long, and Chrome supports just that:
https://chromestatus.com/feature/4946713618939904

So, what happens when the URL of a page is bigger than that, in Dynatrace RUM, in the dtSa cookie?

[ChadTurner]

@AntonioSousa did you get an answer to this question? If so would you mind sharing it with the community? 

[AntonioSousa]

@ChadTurner,

No, I didn't get an answer, and also didn't have the chance to test.

[mhlamine]

Hi,

we are getting a 431 http error Request Header Fields Too Large on some monitored applications.

we are suspecting the dtsa cookie to be the root cause. the size of the cookie exceeds 1024 bytes.

how can we be sure that this is the root cause?

is there a way to truncate that cookie? what are the possible impacts on monitoring?

Regards.

[uros_djukic1]

Hi, 
Please create ticket to the support, it exists some special attributes which could be applied into custom configuration for Javascript tag properties.  Namely, we have possibility to shorten the length of this cookie.
Afterward, you will have 3 options : 
- store the dtSa into sessionstorage if supported 
-  disable it completely
- or change reverse proxy , if it is apache look into configuration in order to increase header size for instance.
Thanks