Skip to content

Commit

Permalink
Script updating gh-pages from f539c38. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Jan 31, 2024
1 parent eb8178a commit 4db3095
Show file tree
Hide file tree
Showing 2 changed files with 37 additions and 32 deletions.
55 changes: 30 additions & 25 deletions draft-ietf-core-oscore-capable-proxies.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1602,7 +1602,7 @@ <h3 id="name-processing-of-an-incoming-r">
<li class="normal" id="section-3.3-2.2.2.2">
<p id="section-3.3-2.2.2.2.1">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.<a href="#section-3.3-2.2.2.2.1" class="pilcrow"></a></p>
<p id="section-3.3-2.2.2.2.2">
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.<a href="#section-3.3-2.2.2.2.2" class="pilcrow"></a></p>
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.<a href="#section-3.3-2.2.2.2.2" class="pilcrow"></a></p>
<p id="section-3.3-2.2.2.2.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.<a href="#section-3.3-2.2.2.2.3" class="pilcrow"></a></p>
<p id="section-3.3-2.2.2.2.4">
Expand Down Expand Up @@ -3795,11 +3795,11 @@ <h2 id="name-state-diagram-processing-of">
<figure id="figure-7">
<div id="appendix-C-2.1">
<div class="alignCenter art-svg artwork" id="appendix-C-2.1.1">
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="1680" width="576" viewBox="0 0 576 1680" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="1696" width="576" viewBox="0 0 576 1696" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
<path d="M 8,224 L 8,304" fill="none" stroke="black"></path>
<path d="M 8,512 L 8,624" fill="none" stroke="black"></path>
<path d="M 8,1040 L 8,1136" fill="none" stroke="black"></path>
<path d="M 8,1520 L 8,1584" fill="none" stroke="black"></path>
<path d="M 8,1520 L 8,1600" fill="none" stroke="black"></path>
<path d="M 32,352 L 32,504" fill="none" stroke="black"></path>
<path d="M 32,672 L 32,1032" fill="none" stroke="black"></path>
<path d="M 32,1144 L 32,1512" fill="none" stroke="black"></path>
Expand All @@ -3821,7 +3821,7 @@ <h2 id="name-state-diagram-processing-of">
<path d="M 224,1360 L 224,1440" fill="none" stroke="black"></path>
<path d="M 232,160 L 232,176" fill="none" stroke="black"></path>
<path d="M 272,448 L 272,464" fill="none" stroke="black"></path>
<path d="M 272,1520 L 272,1584" fill="none" stroke="black"></path>
<path d="M 272,1520 L 272,1600" fill="none" stroke="black"></path>
<path d="M 280,224 L 280,288" fill="none" stroke="black"></path>
<path d="M 280,640 L 280,696" fill="none" stroke="black"></path>
<path d="M 280,776 L 280,872" fill="none" stroke="black"></path>
Expand Down Expand Up @@ -3898,7 +3898,7 @@ <h2 id="name-state-diagram-processing-of">
<path d="M 96,1440 L 224,1440" fill="none" stroke="black"></path>
<path d="M 8,1520 L 272,1520" fill="none" stroke="black"></path>
<path d="M 304,1552 L 376,1552" fill="none" stroke="black"></path>
<path d="M 8,1584 L 272,1584" fill="none" stroke="black"></path>
<path d="M 8,1600 L 272,1600" fill="none" stroke="black"></path>
<polygon class="arrowhead" points="544,696 532,690.4 532,701.6" fill="black" transform="rotate(90,536,696)"></polygon>
<polygon class="arrowhead" points="536,1000 524,994.4 524,1005.6" fill="black" transform="rotate(90,528,1000)"></polygon>
<polygon class="arrowhead" points="520,1432 508,1426.4 508,1437.6" fill="black" transform="rotate(90,512,1432)"></polygon>
Expand Down Expand Up @@ -4165,36 +4165,41 @@ <h2 id="name-state-diagram-processing-of">
<text x="472" y="1540">Deliver</text>
<text x="520" y="1540">the</text>
<text x="568" y="1540">:</text>
<text x="56" y="1556">indicated</text>
<text x="128" y="1556">virtual</text>
<text x="204" y="1556">addressing</text>
<text x="40" y="1556">exact</text>
<text x="88" y="1556">value</text>
<text x="124" y="1556">of</text>
<text x="160" y="1556">these</text>
<text x="224" y="1556">Uri-Path,</text>
<text x="288" y="1556">-NO</text>
<text x="432" y="1556">:</text>
<text x="472" y="1556">request</text>
<text x="516" y="1556">to</text>
<text x="544" y="1556">the</text>
<text x="568" y="1556">:</text>
<text x="64" y="1572">information</text>
<text x="128" y="1572">for</text>
<text x="184" y="1572">proxying?</text>
<text x="56" y="1572">Uri-Host,</text>
<text x="112" y="1572">and</text>
<text x="164" y="1572">Uri-Port</text>
<text x="232" y="1572">Options</text>
<text x="432" y="1572">:</text>
<text x="488" y="1572">application</text>
<text x="568" y="1572">:</text>
<text x="32" y="1588">for</text>
<text x="88" y="1588">proxying?</text>
<text x="500" y="1588">:................:</text>
<text x="16" y="1636">(#)</text>
<text x="52" y="1636">This</text>
<text x="84" y="1636">is</text>
<text x="140" y="1636">determined</text>
<text x="224" y="1636">according</text>
<text x="276" y="1636">to</text>
<text x="304" y="1636">the</text>
<text x="364" y="1636">endpoint's</text>
<text x="464" y="1636">configuration</text>
<text x="48" y="1652">and</text>
<text x="72" y="1652">a</text>
<text x="116" y="1652">possible</text>
<text x="208" y="1652">authorization</text>
<text x="316" y="1652">enforcement.</text>
<text x="16" y="1652">(#)</text>
<text x="52" y="1652">This</text>
<text x="84" y="1652">is</text>
<text x="140" y="1652">determined</text>
<text x="224" y="1652">according</text>
<text x="276" y="1652">to</text>
<text x="304" y="1652">the</text>
<text x="364" y="1652">endpoint's</text>
<text x="464" y="1652">configuration</text>
<text x="48" y="1668">and</text>
<text x="72" y="1668">a</text>
<text x="116" y="1668">possible</text>
<text x="208" y="1668">authorization</text>
<text x="316" y="1668">enforcement.</text>
</g>
</svg><a href="#appendix-C-2.1.1" class="pilcrow"></a>
</div>
Expand Down
14 changes: 7 additions & 7 deletions draft-ietf-core-oscore-capable-proxies.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down

0 comments on commit 4db3095

Please sign in to comment.