I`m trying to develop an optimistic concurency based on the Etag Header. This header is being sent OK on every GET request, but NOT being sent on a POST. Why?
I`m trying to implement an optimistic concurrency control over a web application entities.
I`m attaching an Etag HTTP Header to every URI that represents an entity.
On successive GET requests this header is being sent back as If-None-Match (witch is OK)
The PROBLEM is on a POST request, the ETAG is not being sent back (neither If-None-Match, If-Match, etc..).
My question is : Is this the desired behavior? The browser omits this on purpose on a Http POST?
I`m trying to implement an optimistic concurrency control over a web application entities.
I`m attaching an Etag HTTP Header to every URI that represents an entity.
On successive GET requests this header is being sent back as If-None-Match (witch is OK)
The PROBLEM is on a POST request, the ETAG is not being sent back (neither If-None-Match, If-Match, etc..).
My question is : Is this the desired behavior? The browser omits this on purpose on a Http POST?
모든 댓글 (1)
Hi Daniel,
Do you still have this problem ?
(If you found a solution a link to that may help others)