From 4db3095b0faa6512a3864572caacc9e26465b58b Mon Sep 17 00:00:00 2001 From: ID Bot Date: Wed, 31 Jan 2024 19:20:36 +0000 Subject: [PATCH] Script updating gh-pages from f539c38. [ci skip] --- draft-ietf-core-oscore-capable-proxies.html | 55 +++++++++++---------- draft-ietf-core-oscore-capable-proxies.txt | 14 +++--- 2 files changed, 37 insertions(+), 32 deletions(-) diff --git a/draft-ietf-core-oscore-capable-proxies.html b/draft-ietf-core-oscore-capable-proxies.html index 235bd87..2f5d5d3 100644 --- a/draft-ietf-core-oscore-capable-proxies.html +++ b/draft-ietf-core-oscore-capable-proxies.html @@ -1602,7 +1602,7 @@

  • REQ does not include the Proxy-Scheme Option or the Proxy-Scheme-Number Option, but it includes one or more Uri-Path Options, and/or the Uri-Host Option, and/or the Uri-Port Option.

    -If the endpoint is not configured to be a reverse-proxy, or what is targeted by the virtual addressing information in the Uri-Path, Uri-Host, or Uri-Port Options is not intended to support reverse-proxy functionalities, then the endpoint proceeds to step 3.

    +If the endpoint is not configured to be a reverse-proxy, or what is targeted by the value of the Uri-Path, Uri-Host, and Uri-Port Options is not intended to support reverse-proxy functionalities, then the endpoint proceeds to step 3.

    Otherwise, the endpoint MUST check whether forwarding this request to (the next hop towards) the origin server is an acceptable operation to perform, according to the endpoint's configuration and a possible authorization enforcement. This check can be based, for instance, on the specific OSCORE Security Context that the endpoint used to decrypt the incoming message, before performing this step.

    @@ -3795,11 +3795,11 @@

    - + - + @@ -3821,7 +3821,7 @@

    - + @@ -3898,7 +3898,7 @@

    - + @@ -4165,36 +4165,41 @@

    Deliver the : - indicated - virtual - addressing + exact + value + of + these + Uri-Path, -NO : request to the : - information - for - proxying? + Uri-Host, + and + Uri-Port + Options : application : + for + proxying? :................: - (#) - This - is - determined - according - to - the - endpoint's - configuration - and - a - possible - authorization - enforcement. + (#) + This + is + determined + according + to + the + endpoint's + configuration + and + a + possible + authorization + enforcement.

    diff --git a/draft-ietf-core-oscore-capable-proxies.txt b/draft-ietf-core-oscore-capable-proxies.txt index aaaeba9..c13216c 100644 --- a/draft-ietf-core-oscore-capable-proxies.txt +++ b/draft-ietf-core-oscore-capable-proxies.txt @@ -687,10 +687,9 @@ Table of Contents Option. If the endpoint is not configured to be a reverse-proxy, or - what is targeted by the virtual addressing information in the - Uri-Path, Uri-Host, or Uri-Port Options is not intended to - support reverse-proxy functionalities, then the endpoint - proceeds to step 3. + what is targeted by the value of the Uri-Path, Uri-Host, and + Uri-Port Options is not intended to support reverse-proxy + functionalities, then the endpoint proceeds to step 3. Otherwise, the endpoint MUST check whether forwarding this request to (the next hop towards) the origin server is an @@ -2160,9 +2159,10 @@ Appendix C. State Diagram: Processing of Incoming Requests v | | v +--------------------------------+ | .................. | Am I a reverse-proxy using the | | : Deliver the : - | indicated virtual addressing |-NO---------+ : request to the : - | information for proxying? | : application : - +--------------------------------+ :................: + | exact value of these Uri-Path, |-NO---------+ : request to the : + | Uri-Host, and Uri-Port Options | : application : + | for proxying? | :................: + +--------------------------------+ (#) This is determined according to the endpoint's configuration