Both 406 and 415 error codes should be described

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Normative
    • Resource Definitions
    • 2.6.0.1.4
    • Hide

      In http://hl7.org/fhir/formats.html#wire, the mentioned 415 status code should become 406.

      Expand this section to explain that this is the case for all reads asking for an unsupported format and the server should return 415 if the format is not supported on a write.

      Show
      In http://hl7.org/fhir/formats.html#wire, the mentioned 415 status code should become 406. Expand this section to explain that this is the case for all reads asking for an unsupported format and the server should return 415 if the format is not supported on a write.
    • Grahame Grieve/Rick Geimer: 9-0-0
    • Correction
    • Non-compatible
    • STU3

      The formats page states that servers should respond with a 415 if they receive a request for a capability statement in a format they cannot support. However, this should be a 406.

      406: If the server cannot respond in accordance with the Accept header: https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7

      415: If the server cannot understand/process the data in the body as defined by the Content-Type header (which describes the entity format): https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.16

      It's typical to see 406 responses on reads and 415 on writes, but it is essentially driven by which header is in conflict. We should describe this distinction in error handling within the format page.

            Assignee:
            Unassigned
            Reporter:
            Jenni Syed
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: