[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-419) Specify ETag handling more precisely
[ http://tools.oasis-open.org/issues/browse/ODATA-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-419:
-----------------------------
Description:
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.
was:
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".
> Specify ETag handling more precisely
> ------------------------------------
>
> Key: ODATA-419
> URL: http://tools.oasis-open.org/issues/browse/ODATA-419
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData Protocol
> Affects Versions: V4.0_CSD01
> Reporter: Ralf Handl
> Fix For: V4.0_CSD02
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]