You can transfer the password into a hash on clientside before it is sent anywhere and then do hash comparison serverside.
But you have the same problem with a Post or Get request ... itis always the same if you don't use SSL, however in the light of the NSA ordeal, even that seems less secure.
EDIT
It could makes sense if you convert the password hash clientside and store it in a hidden field and send it off for comparison instead of sending the password. This however poses the threat that hashes could be collected directly client-side Further it would be bad cause you would also need to expose your seeding (which you should be using anyhow) etc. it is a flawed approach.
Use SSL and be done with it.
You could however bloat your request with http://www.jcryption.org which is based on jQuery