Only for webhook

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Subscription Request
    • Hide

      We will update the specification to clarify that normative language around querystring parameters only applies to webhooks. 

      We'll do this either by creating a section of the spec dedicated to webhook-specific requirements/considerations or by adding a phrase like

      >for `hub.channel.type=webhook`, the hub SHALL ...

      Show
      We will update the specification to clarify that normative language around querystring parameters only applies to webhooks.  We'll do this either by creating a section of the spec dedicated to webhook-specific requirements/considerations or by adding a phrase like >for `hub.channel.type=webhook`, the hub SHALL ...
    • Eric Martin / Bill Wallace: 8-0-0
    • Clarification
    • Compatible, substantive

      Only for webhook section.

      Existing Wording:

      The webhook callback URL MAY contain arbitrary query string parameters (e.g., ?foo=bar&red=fish). Hubs SHALL preserve the query string during subscription verification by appending new, Hub-defined, parameters to the end of the list using the & (ampersand) character to join. When sending the event notifications, the Hub SHALL make a POST request to the callback URL including any query string parameters in the URL portion of the request, not as POST body parameters.

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: