Product managers cannot avoid reading the interface documentation in their work. I hope this article can help you better understand the interface. Interface, that is, the client (browser) submits a request to the server, and the server returns a response to bulk sms service the client. The essence is the transmission and reception of data. This article mainly introduces the basic knowledge related to interfaces, including interface requests and responses, interface types, bulk sms service and network protocols. 1. Request and Response 1. Let's take a look at the request first It is mainly divided into 3 parts: General,
Request Headers, Form Data. Let's take a look at the details of each part. For the General part, we can focus on mastering the following three pieces bulk sms service of information. Request URL represents the requested Url address; Request Method represents the request method. Commonly used request methods are Get, Post, Put, Delete. Among them, the two most widely used are Get and Post. Generally, Get requests are used to obtain data, and Post requests are used to send data; Status Code represents the status code. Common status codes include the following bulk sms service categories this example, 200 OK indicates that the request has been processed normally. Request Headers is the request header,
We will introduce the main fields one by one; Accept: Tell the server the file types we can accept, and the server uses the Content-Type response header to inform the client of its choice; Accept-Language: the language used by the client; Accept-Encoding: The bulk sms service encoding format that the client can accept gzip: Compressed bytes, in order to save bandwidth, the content sent by the server is first compressed by gzip and sent to the client, and then the client decompresses and displays it. HTTP 2.0 can compress the header part HTTP1.1 can only compress the bulk sms service body part; Connection: There are 2 types, namely long connection and short connection: Keep-Alive-Long connection: