28 Nov 2022
01:50 PM
- last edited on
28 Nov 2022
02:07 PM
by
Karolina_Linda
Hello. Can anybody tell me - max length of x-dynatrace header. Customer setting up firewall rules, so they need max length all request headers to allow application work, otherwise requests are blocked.
Thanks.
Alex
Solved! Go to Solution.
28 Nov 2022 01:59 PM
I don't believe there is a size limit from a Dynatrace perspective. Typically, the HTTP header size limit is dependent on the server. (Apache, Nginx, IIS, Tomcat)
28 Nov 2022 02:19 PM
I need value from Dynatrace. Expected answer - for example 200 symbols.
Look like this:
FW4;-712055999;35;-1057699572;862004;0;1310537445;1367;c15c;2h01;3hc0f4c90c;4h0d2734;6h6765016c4c42ea4085044906606ef4e6;7hc487f83ef5f244e3
This header added by Dynatrace. Only Dynatrace can know it. The question is not about web server settings.
Thanks,
Alex
29 Nov 2022 06:46 AM
Hi,
Unfortunately the header length is not fixed. Depending on the situation encoded binary info will be added to header.
Harry
30 Nov 2022 09:58 AM
Thanks for fast response.
03 Apr 2025 09:15 AM
Hello Harald,
We use Dynatrace for mainframe Cobol under CICS and have used a TAG buffer length of 100 bytes for the stubs based on the examples in your documentation.
Now it has turned out that the length can also be greater than 100 bytes and we are having problems processing it correctly.
We know that the length is not fixed. In our tests, with different applications, we see lengths of 74 bytes, 85 bytes, 142 bytes.
What length would you recommend so that we can most likely cover all possible cases in the future?
Thanks
BR; Rene
03 Apr 2025 09:53 AM
Hi Rene,
170 characters should be sufficient, if no custom tags are propagated.
Harry
03 Apr 2025 10:25 AM - edited 03 Apr 2025 10:26 AM
The x-dynatrace header can contain different content as it is used for e.g. web RUM and mobile RUM - see https://docs.dynatrace.com/docs/shortlink/rum-firewall
For mobile RUM the header content can vary in length, but is just calculated it and a max size of 150 chars for the header value (excluding x-dynatrace: name) should be save.
I can't speak for web RUM here where this header is set on OneAgent - so you probably will need a solution using biggest possible value for all scenarios.