Timeline for HTTP POST with URL query parameters -- good idea or not?
Current License: CC BY-SA 2.5
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 5, 2017 at 12:07 | comment | added | Sara | downvote, reasons already explained by @Gareth and @Powerlord ... <form method='POST' action='/Books?bookCode=1234'> <input type='submit' name='Post Me!' /> </form> | |
| Feb 5, 2013 at 15:53 | comment | added | Powerlord | @Jez: The may depend entirely on the browser, considering HTML4 doesn't say to do that. I haven't looked at what HTML5 says on the subject, but keep in mind that this answer was written nearly 4 years ago and HTML5 was only finalized a few months ago. | |
| Feb 5, 2013 at 14:43 | comment | added | Jez | @Powerlord This is just wrong. Try setting up a form to POST with an action of eg. /Books?bookCode=1234. The web server will get POST form vars and a query string. | |
| May 22, 2011 at 14:51 | comment | added | Murali VP | @Bemrose, interpreting standard as you please? | |
| Feb 28, 2010 at 17:13 | comment | added | Gareth | By the way, I also thought that it wasn't possible to mix GET and POST. I just can't find any justification for that behaviour in the spec, and I don't think that your interpretation matches what's written there | |
| Feb 28, 2010 at 17:10 | comment | added | Gareth | Right, but the method attribute just defines how the "form data set" is included in the request. When the method is POST, there's no mention of changing the URI in the form's action. And any URI can of course already contain a query string part. | |
| Feb 27, 2010 at 19:35 | comment | added | Powerlord | @Gareth: It's implicit in the description of the method attribute. You can only set it to get or post, not both. | |
| Feb 27, 2010 at 12:04 | comment | added | Gareth | That snippet doesn't appear on the page you linked to | |
| Aug 3, 2009 at 14:49 | comment | added | aehlke | Mixing GET with POST is just a really bad idea - terribly breaking HTTP and for no good reason. | |
| Mar 4, 2009 at 19:30 | comment | added | Steven Huwig | That's a decent argument, but I think modern browser's Javascript implementations kind of make it a moot point. I'll think about it though -- it is compelling in a future-proofing kind of way. Just because I'm not using a form for it now doesn't mean I won't want to later. | |
| Mar 4, 2009 at 19:16 | history | answered | Powerlord | CC BY-SA 2.5 |