Updates the configuration of the allowed beacon origins for Cross Origin Resource Sharing (CORS) requests.
The request consumes an application/json payload.
| PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/allowedBeaconOriginsForCors |
| Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/allowedBeaconOriginsForCors |
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 allowed beacon origins for CORS requests.
AllowedBeaconOrigins objectConfiguration of the allowed beacon origins for CORS requests.
A list of allowed beacon origins for CORS requests.
Discard (true) or keep (false) beacons without the Origin HTTP header on the BeaconForwarder.
If not set, false is used.
BeaconDomainPattern objectAllowed beacon origin for CORS requests.
The matching operation for the domainNamePattern.
CONTAINSENDS_WITHEQUALSSTARTS_WITHThe pattern of the allowed domain name.
ConfigurationMetadata objectMetadata useful for debugging
Dynatrace version.
A sorted list of the version numbers of the configuration.
A sorted list of version numbers of the configuration.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"allowedBeaconOrigins": [{"domainNameMatcher": "EQUALS","domainNamePattern": "dynatrace.com"}],"metadata": {"clusterVersion": "Mock version","configurationVersions": [4,2]}}
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/allowedBeaconOriginsForCors/validator |
| Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/allowedBeaconOriginsForCors/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.