You can just use post transmission directly. Regarding security, please read the information related to signature verification. There are other ways to ensure it.
To put data into the body, it must be retrieved through POST, which is restricted by the HTTP protocol.
Since data is to be transmitted, use POST.
What GET passes is not data, but other additional parameters. When the url cannot describe a uri resource in detail, use parameters to assist, such as paging, sorting, etc...
Theoretically there is no essential difference between GET and POST, so it is recommended to use POST.
Also, if you must use GET, it is recommended to put the data to be transmitted in the same object. For example, the content you want to transmit is:
You can first construct the object to be transmitted (for example, use JSON format, other formats do not matter):
Then encrypt this object, for example, get the ciphertext:
Do URL Encode again and transmit:
You can just use post transmission directly. Regarding security, please read the information related to signature verification. There are other ways to ensure it.
To put data into the body, it must be retrieved through POST, which is restricted by the HTTP protocol.
Since data is to be transmitted, use POST.
What GET passes is not data, but other additional parameters. When the url cannot describe a uri resource in detail, use parameters to assist, such as paging, sorting, etc...