2015May core #1244 - Clarify content-location for Reads without Versioning support

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • REST (http)
    • 2.1.0.8
    • Hide

      The Content-Location header will be removed

      Show
      The Content-Location header will be removed
    • Grahame Grieve / Andy Stechishin: 3-0-0
    • Clarification
    • Non-compatible
    • DSTU1 [deprecated]

      Existing Wording: Servers SHOULD return an ETag header with the versionId and a Content-Location header with the response which is the full version specific url (see vread below) and a Last-Modified header.

      Proposed Wording: Servers SHOULD return an ETag header with the versionId and a Content-Location header with the response which is the full version specific url (see vread below) and a Last-Modified header. If servers do not support full versioning, the content-location header SHOULD be populated with the logical ID URL.

      Comment:

      Provide additional clarification on behavior when versioning is not supported

            Assignee:
            Unassigned
            Reporter:
            seanmoore
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: