In the above figure, you can see the request method and path parsed by the server, and when using the GET method, you
need to specify the access path in the serial data (remember to add "?") and spaces)
The GET method is more flexible and suitable for small data uploads, but the request path often becomes a
situation.
3.3.4 HTTP Client Precautions
The access path set by the AT command is only valid for the POST request method, and the GET method requires the
data header in the serial data to specify the access path.
The GET method requires the data header in the serial data to specify the access path.
The default request header attributes of the HTTP client are
Host: xxx.xxx.xxx.xxx
Accept: */* Content-Length: xx
This ensures that the client can request data without setting the packet header.
The customer can set the header information by using the data format AT+HCHEAD=XX:XX,XXX:XXX. If the
customer wants to add the default request header followed by
Connection: keep-alive
Content-Type: application/json
then the following AT format should be used, with a total length of no more than 180 bytes.
AT+HCHEAD= Connection: keep-alive, Content-Type: application/json
3.4 Multi-link mode for servers (MULTIS)
When the module works in MULTIS mode, other modes or sub-functions will not be used, MULTIS i.e. the module as a
server can support multiple client connection mode, currently the mode supports simultaneous 4-way client connection,
the following, will show the module in the role of AP to achieve multi-client communication.
3.4.1 Setting process
1. Enter AT mode, so that the current network role is in AP mode
+++ AT+ROLE=AP
2. Switch the mode and set the working mode to MULTIS mode AT+MODE=MULTIS
3. set the local listening port number of MULTIS (default 5001) AT+MULTISP=5002
4,reboot to take effect command AT+RST
