How secure is a HTTP POST?

by

SSL is a must.

POST method is not more secure than GET as it also gets sent unencrypted over network.

SSL will cover the whole HTTP communication and encrypt the HTTP data being transmitted between the client and the server.

More Related Contents:

  1. Are HTTPS headers encrypted?
  2. Pure JavaScript Send POST Data Without a Form
  3. Send POST data using XMLHttpRequest
  4. Fundamental difference between Hashing and Encryption algorithms
  5. What is the best way to implement “remember me” for a website? [closed]
  6. JWT (JSON Web Token) automatic prolongation of expiration
  7. Will web browsers cache content over https
  8. Best way to handle security and avoid XSS with user entered URLs
  9. Is it possible to reverse a SHA-1?
  10. How do you protect your software from illegal distribution? [closed]
  11. How can I throttle user login attempts in PHP
  12. Why is using a Non-Random IV with CBC Mode a vulnerability?
  13. Post form data using HttpWebRequest
  14. What is happening when I have two CSP (Content Security Policies) policies – header & meta?
  15. Username and password in https url
  16. What is the difference between a cer, pvk, and pfx file?
  17. Why do salts make dictionary attacks ‘impossible’?
  18. If you use HTTPS will your URL params will be safe from sniffing? [duplicate]
  19. When the bots attack! [closed]
  20. Should I impose a maximum length on passwords?
  21. Use App Scripts to open form and make a selection
  22. SSO with CAS or OAuth?
  23. What’s the best approach for generating a new API key?
  24. Best practices for server-side handling of JWT tokens [closed]
  25. How do I secure REST API calls?
  26. What are best practices for securing the admin section of a website? [closed]
  27. How can I hash passwords in postgresql?
  28. How is it possible to access memory of other processes?
  29. How do you protect code from leaking outside? [duplicate]
  30. Has Hardware Lock Elision gone forever due to Spectre Mitigation?

Leave a Comment