- From: James M Snell <jasnell@gmail.com>
- Date: Thu, 19 Nov 2020 06:25:25 -0800
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Received on Thursday, 19 November 2020 14:25:54 UTC
Heh, I think we had a similar discussion before when we first started writing this up if memory serves me correctly ;) ... My view of it should definitely not limit anyone else's here, or hold up the WG adopting the draft ;) On Wed, Nov 18, 2020, 20:50 Julian Reschke <julian.reschke@gmx.de> wrote: > . > > > > > > To be clear, this is not intended as a safe, idempotent equivalent to > > POST. It is intended specifically to cover search/query operations which > > are often ambiguously represented as GET or POST. I'm not quite sure > > what a safe idempotent equivalent to POST would even be, but this is not > > it. > > ... > > FWIW, I disagree with that. Ignore the method name for a moment, and > what's left is a retrieval operation similar to GET which additionally > takes the request payload into account. > > > ... > > Best regards, Julian > >
Received on Thursday, 19 November 2020 14:25:54 UTC