From 636b48ab51a0dbae6f91a397e1e153cd0b9a050d Mon Sep 17 00:00:00 2001 From: Tim <154928639+TimothyKopec@users.noreply.github.com> Date: Thu, 30 May 2024 11:12:38 -0500 Subject: [PATCH 1/3] change to Hub generated open Event https://jira.hl7.org/browse/FHIR-45714 --- input/pagecontent/2-4-Subscribing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/input/pagecontent/2-4-Subscribing.md b/input/pagecontent/2-4-Subscribing.md index 6f954ed3..2292e031 100644 --- a/input/pagecontent/2-4-Subscribing.md +++ b/input/pagecontent/2-4-Subscribing.md @@ -55,7 +55,7 @@ hub.channel.type=websocket&hub.mode=subscribe&hub.topic=fdb2f928-5546-4f52-87a0- Upon receiving subscription or unsubscription requests, the Hub SHALL respond to a subscription request with an appropriate HTTP response. -If a Hub refuses the request or finds any errors in the subscription request, an appropriate HTTP error response code (4xx or 5xx) SHALL be returned. In the event of an error, the Hub SHOULD return a description of the error in the response body as plain text, to be used by the client developer to understand the error. This is not meant to be shown to the end user. Hubs MAY decide to reject some subscription requests based on their own policies, for example, a Hub may require that all applications subscribe to the same set of events. +If a Hub refuses the request or finds any errors in the subscription request, an appropriate HTTP error response code (4xx or 5xx) SHALL be returned. In the event of an error, the Hub SHOULD return a description of the error in the response body as plain text, to be used by the client developer to understand the error. This is not meant to be shown to the end user. Hubs MAY decide to reject some subscription requests based on their own policies, for example, in lieu of a Hub generated open events it may require that all applications subscribe to the same set of events. This can be found in [Hub Generated open Events](https://build.fhir.org/ig/HL7/fhircast-docs/2-5-EventNotification.html#hub-generated-open-events). In the case of an acceptable subscription request, an HTTP 202 "Accepted" response is returned. This indicates that the request was received and will now be verified by the Hub. The HTTP body of the response SHALL consist of a JSON object containing an element name of `hub.channel.endpoint` and a value for the WSS URL. The WebSocket WSS URL SHALL be cryptographically random, unique, and unguessable. From 98bb53cacf0ea34d97ad88d6d8560cf60f4e9eb4 Mon Sep 17 00:00:00 2001 From: Isaac Vetter Date: Thu, 30 May 2024 11:25:14 -0500 Subject: [PATCH 2/3] Update input/pagecontent/2-4-Subscribing.md --- input/pagecontent/2-4-Subscribing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/input/pagecontent/2-4-Subscribing.md b/input/pagecontent/2-4-Subscribing.md index 2292e031..33862809 100644 --- a/input/pagecontent/2-4-Subscribing.md +++ b/input/pagecontent/2-4-Subscribing.md @@ -55,7 +55,7 @@ hub.channel.type=websocket&hub.mode=subscribe&hub.topic=fdb2f928-5546-4f52-87a0- Upon receiving subscription or unsubscription requests, the Hub SHALL respond to a subscription request with an appropriate HTTP response. -If a Hub refuses the request or finds any errors in the subscription request, an appropriate HTTP error response code (4xx or 5xx) SHALL be returned. In the event of an error, the Hub SHOULD return a description of the error in the response body as plain text, to be used by the client developer to understand the error. This is not meant to be shown to the end user. Hubs MAY decide to reject some subscription requests based on their own policies, for example, in lieu of a Hub generated open events it may require that all applications subscribe to the same set of events. This can be found in [Hub Generated open Events](https://build.fhir.org/ig/HL7/fhircast-docs/2-5-EventNotification.html#hub-generated-open-events). +If a Hub refuses the request or finds any errors in the subscription request, an appropriate HTTP error response code (4xx or 5xx) SHALL be returned. In the event of an error, the Hub SHOULD return a description of the error in the response body as plain text, to be used by the client developer to understand the error. This is not meant to be shown to the end user. Hubs MAY decide to reject some subscription requests based on their own policies. For example, a Hub may require that all applications subscribe to the same set of events in lieu of [deriving open events](https://build.fhir.org/ig/HL7/fhircast-docs/2-5-EventNotification.html#hub-generated-open-events). In the case of an acceptable subscription request, an HTTP 202 "Accepted" response is returned. This indicates that the request was received and will now be verified by the Hub. The HTTP body of the response SHALL consist of a JSON object containing an element name of `hub.channel.endpoint` and a value for the WSS URL. The WebSocket WSS URL SHALL be cryptographically random, unique, and unguessable. From ee7deef6541d4b6bb799defb42e108e102eafd58 Mon Sep 17 00:00:00 2001 From: Isaac Vetter Date: Fri, 30 Aug 2024 11:00:11 -0500 Subject: [PATCH 3/3] don't use absolute urls --- input/pagecontent/2-4-Subscribing.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/input/pagecontent/2-4-Subscribing.md b/input/pagecontent/2-4-Subscribing.md index 33862809..0e1acaae 100644 --- a/input/pagecontent/2-4-Subscribing.md +++ b/input/pagecontent/2-4-Subscribing.md @@ -55,7 +55,8 @@ hub.channel.type=websocket&hub.mode=subscribe&hub.topic=fdb2f928-5546-4f52-87a0- Upon receiving subscription or unsubscription requests, the Hub SHALL respond to a subscription request with an appropriate HTTP response. -If a Hub refuses the request or finds any errors in the subscription request, an appropriate HTTP error response code (4xx or 5xx) SHALL be returned. In the event of an error, the Hub SHOULD return a description of the error in the response body as plain text, to be used by the client developer to understand the error. This is not meant to be shown to the end user. Hubs MAY decide to reject some subscription requests based on their own policies. For example, a Hub may require that all applications subscribe to the same set of events in lieu of [deriving open events](https://build.fhir.org/ig/HL7/fhircast-docs/2-5-EventNotification.html#hub-generated-open-events). +If a Hub refuses the request or finds any errors in the subscription request, an appropriate HTTP error response code (4xx or 5xx) SHALL be returned. In the event of an error, the Hub SHOULD return a description of the error in the response body as plain text, to be used by the client developer to understand the error. This is not meant to be shown to the end user. Hubs MAY decide to reject some subscription requests based on their own policies. For example, a Hub may require that all applications subscribe to the same set of events in lieu of [deriving open events](2-5-EventNotification.html#hub-generated-open-events). + In the case of an acceptable subscription request, an HTTP 202 "Accepted" response is returned. This indicates that the request was received and will now be verified by the Hub. The HTTP body of the response SHALL consist of a JSON object containing an element name of `hub.channel.endpoint` and a value for the WSS URL. The WebSocket WSS URL SHALL be cryptographically random, unique, and unguessable.