Timeline for What is a typical response from webserver for POST request?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Oct 16, 2015 at 19:29 | comment | added | k1DBLITZ | @DoodleKana Correct, the HTTP status code is irrelevant. There is a distinction between Post data and form field data. Post payload is not cached but form field data can be cached. To prevent form field data from being cached, please refer to stackoverflow.com/questions/2699284/… | |
| Oct 15, 2015 at 21:37 | comment | added | DoodleKana | @gowenfawr Ok if I am understanding this correctly, as long as the response header to POST has no-cache it does not matter whether the response is 200 or 302 since RFC said it will not be cached if it is not 303 or header has caching allowed. Am I right? | |
| Oct 15, 2015 at 20:32 | history | edited | gowenfawr | CC BY-SA 3.0 |
Updated to reflect scope change.
|
| Oct 15, 2015 at 20:18 | comment | added | Neil Smithline | @Zonk and gowenfawr - see recent response on the OP - it's unlcear which is being talked about but likely the request. | |
| Oct 15, 2015 at 19:52 | comment | added | gowenfawr | @Zonk, At the point he's describing possibly using a 302 instead of a 200, he's talking about the response, not the request. Requests don't get numbers :). | |
| Oct 15, 2015 at 19:51 | comment | added | Zonk | I think @DoodleKana means caching of the POST request. | |
| Oct 15, 2015 at 19:45 | history | edited | gowenfawr | CC BY-SA 3.0 |
added 218 characters in body
|
| Oct 15, 2015 at 19:40 | history | answered | gowenfawr | CC BY-SA 3.0 |