Skip to content

Optional Http Headers

Jump to bottom Edit New page
Dan Leech edited this page Dec 16, 2014 · 4 revisions

 

 

 

DOCS HAVE MOVED

This wiki is no longer maintained and should not be used. Read the Event Store docs at docs.geteventstore.com.

The latest version of the page you are currently viewing is available here.

 

 

 

The Event Store supports the use of a few custom HTTP headers for requests.

Note that the headers have previously been in the form "X-ES-ExpectedVersion" but have been changed to ES-ExpectedVersion in compliance with RFC-6648 http://tools.ietf.org/html/rfc6648

The headers that are currently supported are:

  • ES-ExpectedVersion The expected version of the stream (allows optimistic concurrency)
  • ES-ResolveLinkTo Whether or not to resolve linkTos in stream
  • ES-RequiresMaster Whether this operation needs to be run on the master node
  • ES-TrustedAuth Allows a trusted intermediary to handle authentication
  • ES-LongPoll Instructs the server to do a long poll operation on a stream read
  • ES-HardDelete Instructs the server to hard delete the stream when deleting as opposed to the default soft delete
  • ES-EventType Instructs the server the event type associated to a posted body
  • ES-EventId Instructs the server the event id associated to a posted body Google analytics pixel
Add a custom footer
Add a custom sidebar

Clone this wiki locally