Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

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?

  • 1 ŋuɖoɖo
  • 2 masɔmasɔ sia le wosi
  • 7 views
  • Nuɖoɖo mlɔetɔ John99

daniel.cristian
daniel.cristian
more options

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?

All Replies (1)

John99
John99
more options

Hi Daniel,

Do you still have this problem ?

(If you found a solution a link to that may help others)