Updates the list of IP detection headers.
The request consumes an application/json payload.
| PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/geographicRegions/ipDetectionHeaders |
| Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/geographicRegions/ipDetectionHeaders |
To execute this request, you need an access token with WriteConfig scope.
To learn how to obtain and use it, see Tokens and authentication.
The JSON body of the request. Contains the configuration of the custom client IP headers.
IpDetectionHeaders objectConfiguration of the custom client IP headers.
A list of custom client IP headers.
Headers are evaluated from top to bottom; the first matching header applies.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"ipDetectionHeaders": ["string"]}
Success. The configuration has been updated. Response doesn't have a body.
We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.
The request consumes an application/json payload.
| POST | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/geographicRegions/ipDetectionHeaders/validator |
| Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/geographicRegions/ipDetectionHeaders/validator |
To execute this request, you need an access token with WriteConfig scope.
To learn how to obtain and use it, see Tokens and authentication.
Success. The submitted configuration is valid. Response doesn't have a body.