PurePath Metadata vs. Client-side metadata - different http response codes

[kalle_lahtinen]

Hi,

I'm seeing failed PurePaths which are interpeted as 500 errors by Dynatrace. However, the client-side metadata says that the response status for POST was 200 OK. How should I interpret this? Server says 500, client sees 200...?

[skrystosik]

Only Idea I have is that you have reverse proxy for example before Tomcat which is returning 200 codes always to client with error message because 500 error is handled somehow. I'm not sure but maybe it can be achieved on Tomcat itself 🙂

Sebastian

[kalle_lahtinen]

Thanks Sebastian, seems like a possible scenario. I guess I'll just have to try and dig more info from the devs about this. I was just really surprised to see it, I think this is the first time I've noticed a single PurePath contain two different http response codes simultaneously 🙂 But something like you described does indeed make sense to me.

[a_caretta]

Hi,

I would like to tag along this conversation because I'm experiencing the same strange issue and, in addition, it isn't predictable since sometimes the requests on the bottom return 500 and sometimes 200 with 500 on client-side metadata.
The right behavior is when 500 takes place, and it causes a 420 on the request above.

I don't have permissions to upload images, otherwise I would have attached them.

Can you help me to better understand how to proceed? where to control?

Thank you,

Andrea