If we use POST, but HTTP (not HTTPS) — what then?

Using POST over HTTP (without HTTPS encryption) means that the data sent in the request body is transmitted in plain text. This poses several risks:

• Data interception: Anyone who can listen to the network (for example, on a public Wi-Fi network) can see the request content, including confidential data.
• Data tampering: The lack of encryption allows malicious actors to modify data in transit.
• Lack of authenticity: Without HTTPS, there is no guarantee that the server you are communicating with is legitimate.

Therefore, POST without HTTPS does not ensure data security, and sensitive information can be compromised. It is always recommended to use HTTPS for data transmission, especially if the data is confidential.