-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GET requests #31
Comments
An updated version of the api.py patch : https://gist.github.com/nberger-git/77f1d8091987eaa19c53 |
What's the motivation for using GET instead of POST in some cases? I'm not sure the additional code complexity is worth the benefit. |
There are 2 major benefits. #1. Server performance. GET operations can be cached with Varnish and This is consistent with RFC1945 Applications must not cache responses to a POST request because the See also http://stackoverflow.com/a/3477374 #2. Logging/Diagnostics. GET params are easily visible in a standard log 184.1.2.3 - - [09/Jun/2016:01:08:31 +0000] "GET is much more useful than 113.1.2.3 - - [08/Jun/2016:02:21:28 +0000] "POST /api.php HTTP/1.1" 200 917 For apache, getting these sorts of details from a POST requires installing https://httpd.apache.org/docs/current/mod/mod_dumpio.html One possible implementation is at And I would be happy to make a pull request, or any requested changes. On Jun 9, 2016 9:21 AM, "MZMcBride" [email protected] wrote:
|
A site maintainer asked if the requests for content could be sent as GET instead of POST, so I made a couple of minor changes in wikitools to support this.
In case you want to propagate something like this to the master, the patch files wrt the current package version are linked here: https://gist.github.com/nberger-git/7fa9bc527c21a11caba2
The text was updated successfully, but these errors were encountered: