You're totally right. Perhaps using a "Content-Location" header might be a better fit for that. Shani.On 18 Nov 2024, at 9:27, Taeyun Kim wrote:Hi,Here are my thoughts:- The value of ETag is (as far as I know) defined as an opaque string by the specification, meaning the client shouldn’t interpre
Hi,
Here are my thoughts:
- The value of ETag is (as far as I know) defined as an opaque string by the
specification, meaning the client shouldn’t interpret or assign any
significance to it, regardless of what the server specifies. It’s best to avoid
the client giving any particular meaning to
Using the metadata file name as ETag is nice way to go. In that case, adding HEAD method support to the loadTable endpoint will return the latest metadata pointer, which can be used to support "isLatest" without returning the body. It can be also leveraged in order to return the latest metadata loc
+1 (binding)
Verified checksums, signatures, and tests. Thanks Matt!
Thanks,
Amogh Jahagirdar
On Fri, Nov 15, 2024 at 9:42 AM Fokko Driesprong wrote:
> +1 (binding)
>
> Verified checksums, signatures, and tests with the validation script using
> the Apache dist (thanks Kevin!). Did some checks
Hi,
To Gabor:
It doesn’t seem necessary to interpret HTTP caching literally in this context.
Simply using the HTTP headers defined by HTTP caching to check the freshness of
metadata should be sufficient.
There’s no requirement for the client to duplicate or store cached HTTP
responses.
To Yufei
