What security issues do you see in transmitting login and password via URL query parameters?

Transmitting login and password through query parameters in the URL poses several serious security issues:

• Logs and browser history: URLs with parameters are stored in browser history and can be captured in web server logs, proxies, and other intermediate systems, increasing the risk of credential leaks.
• Caching: Some browsers and proxies may cache URLs, including parameters, which also raises the risk of compromise.
• Lack of encryption: If the connection is not secured with HTTPS, URL parameters are transmitted in plain text.
• Intercept possibility: URLs can be easily copied or intercepted, for example, via the referer when navigating to other sites.

The correct approach is to transmit credentials through the body of a POST request over a secure HTTPS connection, and even better — use authentication mechanisms that do not require transmitting the password with each request (e.g., tokens).