Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Learn More

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 wótegrono
  • 2 matej toś ten problem
  • 7 naglědow
  • Slědne wótegrono wót John99

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?

Wšykne wótegrona (1)

more options

Hi Daniel,

Do you still have this problem ?

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