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.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

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 resposta
  • 2 têm este problema
  • 7 visualizações
  • Última resposta por 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?

Todas as respostas (1)

more options

Hi Daniel,

Do you still have this problem ?

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