FS#49089 - Ability to send POST requests instead of GET
Attached to Project:
AUR web interface
Opened by Alad Wenter (Alad) - Tuesday, 26 April 2016, 11:34 GMT
Last edited by Kevin Morris (kevr) - Saturday, 12 February 2022, 23:25 GMT
Opened by Alad Wenter (Alad) - Tuesday, 26 April 2016, 11:34 GMT
Last edited by Kevin Morris (kevr) - Saturday, 12 February 2022, 23:25 GMT
|
Details
GET requests fail with HTTP 414 errors with a large amount
of requests, for example when querying many packages for AUR
updates [1], or resolving large dependency chains [2]. An
existing workaround is to split requests, but besides the
added means needed to split and merge requests, the
resulting JSON is more difficult to parse.
[1] https://github.com/aurapm/aura/issues/387 [2] https://github.com/AladW/aurutils/issues/111 [3] https://curl.haxx.se/docs/httpscripting.html#POST |
This task depends upon
Closed by Kevin Morris (kevr)
Saturday, 12 February 2022, 23:25 GMT
Reason for closing: Fixed
Additional comments about closing: Live.
Saturday, 12 February 2022, 23:25 GMT
Reason for closing: Fixed
Additional comments about closing: Live.
Comment by Kevin Morris (kevr) -
Friday, 03 July 2020, 16:14 GMT
Comment by Kevin Morris (kevr) -
Friday, 03 July 2020, 16:54 GMT
Comment by Kevin Morris (kevr) -
Monday, 07 February 2022, 10:53 GMT
Working on this.
On a POST request, do we need to support url parameters, or can we
just leave it to the data that's given from the client:
application/json|form data?
https://gitlab.archlinux.org/archlinux/aurweb/-/commit/2dfa41c9a571cc838c6fe937c504d90f50636523
has been merged to live and will be rolled out on next deployment.