Timeline for Https POST Request for POST Parameters
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 5, 2019 at 20:23 | answer | added | mentallurg | timeline score: 0 | |
| Sep 5, 2019 at 16:20 | answer | added | Mike Ounsworth | timeline score: 3 | |
| Sep 5, 2019 at 15:29 | answer | added | Raimonds Liepiņš | timeline score: 0 | |
| Sep 5, 2019 at 15:29 | comment | added | Ghedipunk |
The id/1 part... Is that identifying a resource on your server, or the user? If it's identifying a resource, you most definitely want to leave it in the URL. If it's for the user, then you're much better off using a cookie. POST is generally for submitting forms, and you don't want your site's primary navigation method to be submitting forms the whole time.
|
|
| Sep 5, 2019 at 15:23 | answer | added | keithRozario | timeline score: 1 | |
| Sep 5, 2019 at 15:20 | comment | added | user163495 | More secure against what? What are you trying to protect yourself from? | |
| Sep 5, 2019 at 15:17 | history | asked | Jshee | CC BY-SA 4.0 |