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

Clarify unsubscribe response behavior

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • Subscribing and unsubscribing [deprecated]
    • 2.4.6
    • Hide

      We will clarify that any http response code other than 2xx indicates an error in the unsubscription process (but not dictate an error's meaning for the subscription). 

      Granting editorial discretion, we will add an example of an http 202 response, if it can be worked into the specification while maintaining a high level of readability.

      Show
      We will clarify that any http response code other than 2xx indicates an error in the unsubscription process (but not dictate an error's meaning for the subscription).  Granting editorial discretion, we will add an example of an http 202 response, if it can be worked into the specification while maintaining a high level of readability.
    • Bas van den Heuval / Eric Martin: 5-0-0
    • Clarification
    • Non-substantive

    Description

      Provide specification of unsubscribe response. Example shows a 202--is this always the case? Can an unsubscribe be rejected by the hub (e.g. failed validation)?

      (Comment 15 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            esilver Elliot Silver
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: