- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 1 Nov 2024 07:35:53 +0100
- To: Michael Toomim <toomim@gmail.com>, Josh Cohen <joshco@gmail.com>
- Cc: ietf-http-wg@w3.org
On 01.11.2024 03:07, Michael Toomim wrote: > On 10/31/24 3:03 PM, Josh Cohen wrote: >> Perhaps you should use both. Much like a regular web server if we >> have the resource we return it, if we don't have it, but know where it >> is we send a 3xx. If we don't have it and don't have any known >> address for it, then we return a 404. > > Maybe we should return a 404 Not Found, along with a header > disambiguating to the client that it was the *version* (not the > resource) that was not found. A version *is* an HTTP resource. It has content; it has metadata, it can be retrieved with GET. It seems we need to work on terminology: version-controlled resources (aka versioned resources, mutable), and their versions (snapshots, in general immutable). All of these are HTTP resources, because you can interact with them using HTTP. Best regards, Julian
Received on Friday, 1 November 2024 06:35:59 UTC