UpdateGatewayRouteCORS - Microservices Engine - Alibaba Cloud Documentation Center

Modifies the cross-origin resource sharing (CORS) policy of a route.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
mse:UpdateGatewayRouteCORS	update	Gateway acs:mse:{#regionId}:{#accountId}:instance/{#GatewayUniqueId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
Id	long	Yes	The ID of the associated record.	55
GatewayId	long	No	The ID of the gateway.	85
CorsJSON	object	No	The information about the CORS policy.
Status	string	No	The status of the policy.	off
AllowOrigins	string	No	The origins from which access is allowed.	https://api.aliyun-inc.com/
AllowMethods	string	No	The HTTP methods allowed.	GET,POST
AllowHeaders	string	No	The request headers allowed.	content-type
ExposeHeaders	string	No	The response headers allowed.	*
TimeUnit	string	No	The unit of time.	h
UnitNum	long	No	The value of time.	24
AllowCredentials	boolean	No	The credentials allowed.	true
GatewayUniqueId	string	Yes	The unique ID of the gateway.	gw-f70a6ddf2f0941a2bb997b2d16028f37
AcceptLanguage	string	No	The language of the response. In compliance with RFC 7231, the backend service must return a response based on the language used by the user. No default value. zh-CN: Chinese en-US: English	zh

Response parameters

Parameter	Type	Description	Example
	object	The schema of the response.
RequestId	string	The ID of the request.	41BE990E-44E4-5ED3-AEEB-A276941B1854
HttpStatusCode	integer	The HTTP status code returned.	200
Message	string	The error message.	You are not authorized to perform this operation.
Code	integer	The status code returned.	200
Success	boolean	Indicates whether the request was successful. Valid values: `true`: The request was successful. `false`: The request failed.	true
Data	long	The data structure.	618

Examples

Sample success responses

JSONformat

{
  "RequestId": "41BE990E-44E4-5ED3-AEEB-A276941B1854",
  "HttpStatusCode": 200,
  "Message": "You are not authorized to perform this operation. ",
  "Code": 200,
  "Success": true,
  "Data": 618
}

Error codes

HTTP status code	Error code	Error message	Description
400	IllegalRequest	Invalid request:%s	Invalid request: %s
400	InvalidParameter	Parameter error:%s	Request parameter error: %s
403	NoPermission	You are not authorized to perform this operation:%s	You do not have the permission to use this interface:%s
404	NotFound	Not found:%s	The resource does not exist:%s
500	InternalError	Console error. Try again later:%s	Console error. Try again later: %s

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2022-02-18	Add Operation	View Change Details