W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2020

Re: How to express no matching results in HTTP SEARH method?

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Wed, 04 Nov 2020 16:14:41 +0000
To: Julian Reschke <julian.reschke@gmx.de>
cc: Roberto Polli <robipolli@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <64433.1604506481@critter.freebsd.dk>
--------
Julian Reschke writes:
> Am 04.11.2020 um 16:12 schrieb Roberto Polli:
> > 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...
>
> Cacheability is an open TODO. I agree that it's supposed to be at least
> as cacheable as POST :-).

Please specify that SEARCH results must *always* have a Cache-Control.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Wednesday, 4 November 2020 16:14:58 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 4 November 2020 16:14:59 UTC