[mdx] mdq issue #9: etag in conditional GET
Cantor, Scott
cantor.2 at osu.edu
Sat Jun 14 13:44:30 PDT 2014
On 6/12/14, 1:21 PM, "Ian Young" <ian at iay.org.uk> wrote:
>>As the ETag is always provided using the Last-Modified for subsequent
>> requests is actually not allowed as per RFC2616 so the possibility of
>> using Last-Modified should be removed. This is in sync with the
>> wording in 2.6:
>> Š
>>
>> A metadata request to the same URL, after an initial request, MUST
>> include the following header per
>> section 13.3.4 of RFC 2616 [RFC2616]:
>>
>> If-None-Match
>
>Any other observations on this?
I had that question a few times. If we're mandating clients support ETag,
then I think the other is redundant, and aparently also actually precluded
anyway.
If not, then obviously that means the server has to send both.
-- Scott
More information about the mdx
mailing list