Wait so why is POST safer than GET? | Sololearn: Learn to code for FREE!
New course! Every coder should learn Generative AI!
Try a free lesson
+ 6

Wait so why is POST safer than GET?

28th Mar 2016, 2:09 AM
Donovan
Donovan - avatar
9 Answers
+ 4
because get will reflect the input value but post is not and that's why is safe for generating password forms etc.
22nd Jun 2016, 5:11 PM
Komal Chauhan
Komal Chauhan - avatar
+ 3
because GET will display the value you inputted from the form to the URL unlike the POST, it is invisible
15th Jun 2016, 5:48 PM
Gerry Pantaleon
Gerry Pantaleon - avatar
+ 2
both are equally unsafe if user input is not validated.
14th Jun 2016, 12:50 PM
Rick S
Rick S - avatar
+ 1
POST is safer than GET as it's hidden not in the URL like GET method
7th May 2016, 11:25 PM
Mahmoud EL Banna
Mahmoud EL Banna - avatar
+ 1
Its simple bro, when you are submitting the data from input field if it is not confidential like "username" then you will use GET, and if you are submitting some private information like "password" then you have to use POST method. Note : using GET method will reflect your input field data in URL unlike not in POST method, That's Post is safer then Get method.
1st Jan 2017, 7:49 PM
Javed Saifi
Javed Saifi - avatar
0
post is safer than get
11th Nov 2016, 9:04 AM
betty
betty - avatar
0
As you know, in GET method the values are visible in the URL: http://example.com/login.php?name=foo&pass=bar As you see, the name and pass are visible. Although You can encode them for example to base64. however they are visible. but in POST method, parameters are inside request body not in URL. Note: Both POST and GET are not completely safe. we have to make them safe. but between them, POST is safer.
3rd Jan 2017, 9:31 PM
Saeed Mashhadi
Saeed Mashhadi - avatar
0
When we use GET method, we can see our name and password at URL. So hackers may hack our account.
22nd Jan 2017, 2:12 PM
Lee
Lee - avatar
- 3
Of course POST!
13th Jun 2016, 4:57 PM
#Bargas
#Bargas - avatar