topic Content-type variation on User session export. in Real User Monitoring

Content-type variation on User session export.

pierre_boucher1 — Tue, 03 Mar 2020 10:57:52 GMT

We have issue on exporting user sessions to our dedicated webserver.

We receive correct http requests with a header {"Content-Type"=>"application/json"} and a JSON message in the body.

We also receive many http requests without any content in the body and with a different header {"Content-Type"=>"text/xml; charset=\"utf-8\""}.

Is it an issue ?

Re: Content-type variation on User session export.

pierre_boucher1 — Tue, 03 Mar 2020 11:23:50 GMT

In fact the json message from Dynatrace is rejected by our web server.

Dynatrace show me error :

Exporting user session data to the configured custom REST endpoint https://api-preprod.groupe-psa.com/dev/public/application/newapvrhub/sbox-rum/v1/kafka/topics/service-box-topic?client_id=xxxxxxxxxxxxxxxxx failed: Status: 400: Bad Request - { "httpCode":"400", "httpMessage":"Bad Request", "moreInformation":"The body of the request, which was expected to be JSON, was invalid, and could not be decoded. The json syntax was invalid (invalid trailing character)." }

How can I avoid this error coming from a request built by Dynatrace "User session export" ?

Re: Content-type variation on User session export.

pierre_boucher1 — Fri, 06 Mar 2020 08:10:21 GMT

My excuses. The problem was on my API gateway which transformed the original http requests before forwarding them to the real service.