title: using HTTP Location header to indicate the location of a future resource
body: <p>Following the REST Level 2 specification described in the <a href="https://martinfowler.com/articles/richardsonMaturityModel.html" rel="nofollow noreferrer">Richardson maturity model by Martin Fowler</a> a response to a POST request creating a resource looks something like this:</p>
  <pre><code>HTTP/1.1 201 Created
  Location: slots/1234/appointment
  [various headers]
  
  &lt;appointment&gt;
    &lt;slot id = &quot;1234&quot; doctor = &quot;mjones&quot; start = &quot;1400&quot; end = &quot;1450&quot;/&gt;
    &lt;patient id = &quot;jsmith&quot;/&gt;
  &lt;/appointment&gt;
  </code></pre>
  <p>I would like to follow this model but in my application when an endpoint is called to create a new resource it's added to a queue instead of created immediately and so I'm responding with a HTTP 202 instead of a 201.</p>
  <p>I would also like to include a URL indicating the future location of the content which the user can GET once the queue is processed. Can I leverage the Location HTTP header to be used for this?
  Resulting in something like:</p>
  <pre><code>HTTP/1.1 202 Accepted
  Location: slots/1234/appointment
  </code></pre>
  <p>on <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Location" rel="nofollow noreferrer">MSDN</a> it states this regarding the Location header:</p>
  <blockquote>
  <p>It only provides a meaning when served with a 3xx (redirection) or
  201 (created) status response.</p>
  </blockquote>
  <p>If that's the case what other standardised HTTP alternative is available for such a case?</p>