Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Proxy section #118

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add Proxy section #118

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f1d574d
Add Proxy section
csarven Oct 11, 2024
58d527f
Clarify proxy usage evaluation
csarven Oct 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 21 additions & 2 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -776,8 +776,14 @@ <h2>Table of Contents</h2>
>
</li>
<li class="tocline">
<a class="tocxref" href="#other-predicates"
<a class="tocxref" href="#proxy"
><bdi class="secno">7.</bdi>
<span>Proxy</span></a
>
</li>
<li class="tocline">
<a class="tocxref" href="#other-predicates"
><bdi class="secno">8.</bdi>
<span>Other predicates</span></a
>
</li>
Expand Down Expand Up @@ -1278,8 +1284,21 @@ <h2><bdi class="secno">6.</bdi> <span property="schema:name">Inbox</span></h2>
</div>
</section>

<section id="proxy" inlist="" rel="schema:hasPart" resource="#proxy"><a class="self-link" href="#proxy"></a>
<h2><bdi class="secno">7.</bdi> <span property="schema:name">Proxy</span></h2>
<div datatype="rdf:HTML" property="schema:description">
<p>When an application needs to make a Cross-Origin Resource Sharing (<abbr title="Cross-Origin Resource Sharing">CORS</abbr>) request using the <cite><a href="https://fetch.spec.whatwg.org/#cors-protocol" rel="cito:citesAsAuthority">CORS protocol</a></cite> [<cite><a class="bibref" href="#bib-fetch">FETCH</a></cite>], the recipient server may not participate in CORS or may often be improperly configured for it. This poses challenges for interoperability in environments like Solid.</p>

<p>One way for applications to practically bypass this limitation in some situations is by using a trusted or preferred proxy. An application can discover a resource's advertised proxy via the <code>solid:proxy</code> property. While any resource, such as a storage, could advertise a proxy, applications can also discover an agent's preferred proxy by checking this property in their WebID Profile Document.</p>

<p>Additionally, using a proxy allows applications to mask their <code>Origin</code>, enhancing privacy and security during requests. This capability can further protect user data in decentralised environments, though it may not fully address all related challenges on its own.</p>

<p>An agent's preferred or trusted proxy may not align with their application's. The decision of whether and in what contexts to use any proxy is an evaluation and a balance between the needs of the agent and the application.</p>
</div>
</section>

<section id="other-predicates" inlist="" rel="schema:hasPart" resource="#other-predicates"><a class="self-link" href="#other-predicates"></a>
<h2><bdi class="secno">7.</bdi> <span property="schema:name">Other predicates</span></h2>
<h2><bdi class="secno">8.</bdi> <span property="schema:name">Other predicates</span></h2>
<div datatype="rdf:HTML" property="schema:description">
<p>
A user, a server or an application with appropriate permissions can add
Expand Down