title: HTTP POST response Location header when creating multiple resources
body: <p>The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.5" rel="noreferrer">HTTP/1.1 standard</a> states that if a <code>POST</code> operation results in the creation of a resource, then the response should include a <code>Location</code> header with the address of the new resource.</p>
  
  <blockquote>
    <p>If a resource has been created on the origin server, the response
    SHOULD be 201 (Created) and contain an entity which describes the
    status of the request and refers to the new resource, and a Location
    header (see section 14.30).</p>
  </blockquote>
  
  <p>and in section 14.30,</p>
  
  <blockquote>
    <p>For 201 (Created) responses, the Location is that of the new resource
    which was created by the request.</p>
  </blockquote>
  
  <p>Now suppose that my API allows batch creation of resources by <code>POST</code>ing an array to the collection resource URL. For example:</p>
  
  <pre><code>POST /books
  [
      {
          "name": "The Colour of Magic",
          "published": "1983"
      },
      {
          "name": "The Light Fantastic",
          "published": "1986"
      }
  ]
  </code></pre>
  
  <p>Since two <code>\book\{bookId}</code> resources have been created, what should be the value of the <code>Location</code> header in this case?</p>
  
  <p>The question <a href="https://stackoverflow.com/questions/28128258">Http post response after multiple new resource creation?</a> is similar, but it asks about the response entity, not the headers (and is unanswered).</p>