-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_CSD01
-
Fix Version/s: V4.0_CSD02
-
Component/s: Protocol
-
Labels:None
-
Environment:
[Applied]
-
Proposal:
-
Resolution:
The specification should be more specific about the ETag handling. E.g. should a weak or strong ETag be generated on the server?
This has consequences because [RFC-2616] (chapters 13.3, 14.24 and 14.26) seem to define the ETag handling slightly different than in this spec.
This affects sections "8.3.1 ETag Header", "8.2.3 Header If-Match", "8.2.4 Header If-Non-Match" and "11.4.1.1 Use of ETags for Avoiding Update Conflicts".
Also state whether we expect ETags for collections that advertise actions, or whether we expect the advertised action to contain an action-specific ETag.