From 829711563a7fb4a298042c995413a0aa5f8366ee Mon Sep 17 00:00:00 2001 From: Felix Gerbig <48456355+gerbigf@users.noreply.github.com> Date: Wed, 23 Oct 2024 09:32:21 +0200 Subject: [PATCH 1/3] Update 07_edrs.md --- docs/usage/management-api-walkthrough/07_edrs.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/usage/management-api-walkthrough/07_edrs.md b/docs/usage/management-api-walkthrough/07_edrs.md index 511a4bae2..dcde9a787 100644 --- a/docs/usage/management-api-walkthrough/07_edrs.md +++ b/docs/usage/management-api-walkthrough/07_edrs.md @@ -254,14 +254,15 @@ Once the EDR has been negotiated and stored, the data can be fetched in two ways ## Provider Data Plane -Once the right EDR has been identified using the EDR Management API the current asset/agreement/transfer-process that -you want to transfer, we can use the `endpoint`, `authorization` to make the request. If the HTTP [Asset](01_assets.md) -has been configured to proxy also HTTP verb, query parameters and path segments, they will be forwarded to the backend from the -Provider Data Plane: +Once the right EDR has been identified using the EDR Management API via the correct asset/agreement/transfer-process that +you want to transfer, we can use the `endpoint` and `authorization` information from the EDRto make the request. The `endpoint` +is used as the Host to which the request is sent and the `authorization` is used as the Token in the authorization header. +If the HTTP [Asset](01_assets.md) has been configured to proxy also HTTP verb, query parameters and path segments, +they will be forwarded to the backend by the Provider Data Plane: ```http request GET /subroute?foo=bar HTTP/1.1 -Host: https://consumer-data.plane/api/public +Host: https://provider-data.plane/api/public Authorization: {{TOKEN}} Content-Type: application/json ``` From cad0a74170b0a2959c132d7ed07749a59a7def64 Mon Sep 17 00:00:00 2001 From: Felix Gerbig <48456355+gerbigf@users.noreply.github.com> Date: Wed, 23 Oct 2024 10:06:03 +0200 Subject: [PATCH 2/3] Update docs/usage/management-api-walkthrough/07_edrs.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Rafael Magalhães --- docs/usage/management-api-walkthrough/07_edrs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/usage/management-api-walkthrough/07_edrs.md b/docs/usage/management-api-walkthrough/07_edrs.md index dcde9a787..1c2e3e78b 100644 --- a/docs/usage/management-api-walkthrough/07_edrs.md +++ b/docs/usage/management-api-walkthrough/07_edrs.md @@ -255,7 +255,7 @@ Once the EDR has been negotiated and stored, the data can be fetched in two ways ## Provider Data Plane Once the right EDR has been identified using the EDR Management API via the correct asset/agreement/transfer-process that -you want to transfer, we can use the `endpoint` and `authorization` information from the EDRto make the request. The `endpoint` +you want to transfer, we can use the `endpoint` and `authorization` information from the EDR to make the request. The `endpoint` is used as the Host to which the request is sent and the `authorization` is used as the Token in the authorization header. If the HTTP [Asset](01_assets.md) has been configured to proxy also HTTP verb, query parameters and path segments, they will be forwarded to the backend by the Provider Data Plane: From a00a7a3afc7db8ca33920709d0d61c25000a6bb1 Mon Sep 17 00:00:00 2001 From: Felix Gerbig <48456355+gerbigf@users.noreply.github.com> Date: Wed, 23 Oct 2024 10:08:28 +0200 Subject: [PATCH 3/3] Update 07_edrs.md Added Rafaels Suggestions --- docs/usage/management-api-walkthrough/07_edrs.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/usage/management-api-walkthrough/07_edrs.md b/docs/usage/management-api-walkthrough/07_edrs.md index 1c2e3e78b..aca981f08 100644 --- a/docs/usage/management-api-walkthrough/07_edrs.md +++ b/docs/usage/management-api-walkthrough/07_edrs.md @@ -255,9 +255,11 @@ Once the EDR has been negotiated and stored, the data can be fetched in two ways ## Provider Data Plane Once the right EDR has been identified using the EDR Management API via the correct asset/agreement/transfer-process that -you want to transfer, we can use the `endpoint` and `authorization` information from the EDR to make the request. The `endpoint` -is used as the Host to which the request is sent and the `authorization` is used as the Token in the authorization header. -If the HTTP [Asset](01_assets.md) has been configured to proxy also HTTP verb, query parameters and path segments, +you want to transfer, we can use the `endpoint` and `authorization` information from the EDR to make the request. +In the example below, the `endpoint` is used as the Host to which the request is sent and the `authorization` is used as the +token in the authorization header. + +Note: If the HTTP [Asset](01_assets.md) has been configured to proxy also HTTP verb, query parameters and path segments, they will be forwarded to the backend by the Provider Data Plane: ```http request