The State of HTTP in 2022

Re:The State of HTTP in 2022 by 0xb0565e487 on Saturday December 31, 2022 @10:47PM (#34203389)

Just send a POST request lol

[ Parent | on HN ]

Re:The State of HTTP in 2022 by NickLamp on Saturday December 31, 2022 @11:16PM (#34203540)

I do... but there are good reasons to not want to. If you read the linked spec you can learn for yourself

[ Parent | on HN ]

Re:The State of HTTP in 2022 by HideousKojima on Saturday December 31, 2022 @10:51PM (#34203409)

But you're only "supposed" to use POST with requests that add/modify data, or something silly like that.

In practice, QUERY is most useful for where you want a bunch of different verbs for the same endpoint and need a body.

[ Parent | on HN ]

Re:The State of HTTP in 2022 by duxup on Saturday December 31, 2022 @10:57PM (#34203432)

In practice I think that’s exactly what many people do.

[ Parent | on HN ]

Re:The State of HTTP in 2022 by spiffytech on Saturday December 31, 2022 @10:57PM (#34203431)

QUERY is cacheable.

[ Parent | on HN ]

Re:The State of HTTP in 2022 by est on Sunday January 01, 2023 @01:42AM (#34204213)

... in theory only. Not that many http cache programs support QUERY. And many HTTP middle-boxes bans non GET/POST verbs.

[ Parent | on HN ]

Re:The State of HTTP in 2022 by counttheforks on Sunday January 01, 2023 @07:32AM (#34205807)

For now. Change has to come from somewhere.

[ Parent | on HN ]

Re:The State of HTTP in 2022 by cogman10 on Sunday January 01, 2023 @10:30AM (#34207060)

And retry-able.

[ Parent | on HN ]

Re:The State of HTTP in 2022 by Existenceblinks on Saturday December 31, 2022 @11:00PM (#34203453)

GraphQL is doomed?

[ Parent | on HN ]

Re:The State of HTTP in 2022 by RedShift1 on Sunday January 01, 2023 @03:25AM (#34204649)

No, this would actually be very useful for GraphQL API's.

[ Parent | on HN ]