About the request structure of HTTP/HTTPS GET based on URL

The content of this article is about the request structure of HTTP/HTTPS GET based on URL. It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.

Request structure

We support HTTP/HTTPS GET requests based on URL. Request parameters need to be included in the URL.

The following is an example of an unencoded URL request for CreateSnapshot:

https://ecs.aliyuncs.com/?Action=CreateSnapshot
&DiskId=1033-60053321
&<公共请求参数>

https specifies the request communication protocol.

ecs.aliyuncs.com specifies the ECS service access address (Endpoint).

Action=CreateSnapshot specifies the API to be called, and DiskId=1033-60053321 is the parameter specified by CreateSnapshot.

are public parameters specified by the system.

Communication protocol

Supports HTTP or HTTPS protocol request communication. For higher security, it is recommended that you use the HTTPS protocol to send requests.

When sensitive data is involved, such as user passwords and SSH key pairs, it is recommended to use the HTTPS protocol. For example, when specifying the Password parameter in CreateInstance.

Access address

#The service access address of the ECS API is as shown in the following table.

When you come from other countries or regions, it is recommended to use the center access address in the table below to reduce network latency.

Request Parameters

You need to specify the target operation through the Action parameter, such as Action=StartInstance. You also need to specify other parameters of the interface as well as public request parameters.

Character encoding

Both requests and returned results use UTF-8 character set encoding.

The above is the detailed content of About the request structure of HTTP/HTTPS GET based on URL. For more information, please follow other related articles on the PHP Chinese website!