But if you put the password in a URL, the user’s browser is going to turn around and store that plaintext password in its history, then sync it to the user’s other devices, and then pop it up on their screen in the address bar autocomplete, perhaps when the user is screen sharing or streaming to hundreds of people. The browser does not expect a password to be stored there and will mishandle it.
If the password is going in URLs you already have a problem.
It’s safe for https.
In terms of the transport, sure.
But if you put the password in a URL, the user’s browser is going to turn around and store that plaintext password in its history, then sync it to the user’s other devices, and then pop it up on their screen in the address bar autocomplete, perhaps when the user is screen sharing or streaming to hundreds of people. The browser does not expect a password to be stored there and will mishandle it.
Nah, if you type a password in a url, it gets turned into asterisks. Look: https://google.com/?password********************