2015May core #1212 - Under "identity", it states that if ports differ, the identity of the resource differs, but specifically mentions that http is equivalent to https. This conflicts.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Implementable Technology Specifications
    • REST (http)
    • 2.1.0.1
    • Hide

      Add further clarification: this is not saying that they should be treated as the same, nor that the content itself must be the same,?but that addresses that only differ between http and https?must refer to the same real world identity. This does not imply that systems need to check that this is true.

      Grahame to draft something specific and check with committee and balloter

      Show
      Add further clarification: this is not saying that they should be treated as the same, nor that the content itself must be the same,?but that addresses that only differ between http and https?must refer to the same real world identity. This does not imply that systems need to check that this is true. Grahame to draft something specific and check with committee and balloter
    • Grahame Grieve / Andy Stechishin: 9-0-1
    • Clarification
    • Compatible, substantive
    • DSTU1 [deprecated]

      Comment:

      Under "identity", it states that if ports differ, the identity of the resource differs, but specifically mentions that http is equivalent to https. This conflicts.

      Also, http and https should not be considered identical, there is no digital certificate or authority to verify that the http site is the same host/data provider as the https site.

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

              Created:
              Updated:
              Resolved: