Re: How to express no matching results in HTTP SEARH method? from Roberto Polli on 2020-11-04 (ietf-http-wg@w3.org from October to December 2020)

From: Roberto Polli <robipolli@gmail.com>
Date: Wed, 4 Nov 2020 16:12:25 +0100
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CAP9qbHXnoYWBw3DoiTbnd6=vOfHRUpSi8-j8fYno+f+mAvT-yg@mail.gmail.com>

Hi Julian,

Il giorno mer 4 nov 2020 alle ore 15:22 Julian Reschke
<julian.reschke@gmx.de> ha scritto:
> ... we essentially want to define something that is
> the same as POST, with the additional property of being safe by
> definition. Nothing more specific than that.

Q:  POST is cacheable (under conditions). I was curious why SEARCH is
not cacheable: this can be useful...

R.

Received on Wednesday, 4 November 2020 15:12:49 UTC