Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-31446

HTTPS strongly encouraged, but ws treated as equivalent to wss?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • FHIR R5 Subscriptions Backport (FHIR)
    • 0.1.0 [deprecated]
    • FHIR Infrastructure
    • Channels
    • Hide

      Update documentation (multiple areas within the Websocket channel description) to indicate that Secure Sockets (wss) is recommended.

      Content should mirror the same guidance for https vs. http.

      Show
      Update documentation (multiple areas within the Websocket channel description) to indicate that Secure Sockets (wss) is recommended. Content should mirror the same guidance for https vs. http.
    • Gino Canessa / Yunwei Wang : 10-0-0
    • Clarification
    • Non-substantive

    Description

      Why not push wss as hard as you pushed HTTPS? I think you should.

      Existing Wording:

      1. Client connects to the server via websockets (ws:// or wss://)\.

      (Comment 17 - imported by: Gino Canessa)

      Attachments

        Activity

          People

            ginocanessa Gino Canessa
            Isaac.Vetter Isaac Vetter
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: