From f1d574dc0e60d805bb1f56fca4e4abe23d5e3790 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Fri, 11 Oct 2024 16:42:38 +0200 Subject: [PATCH 1/2] Add Proxy section --- index.html | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 2c2db95..b6e3f66 100644 --- a/index.html +++ b/index.html @@ -776,8 +776,14 @@

Table of Contents

>
  • - 7. + Proxy +
    • +
  • + 8. Other predicates
    • @@ -1278,8 +1284,19 @@

    6. Inbox

    +
    +

    7. Proxy

    +
    +

    When an application needs to make a Cross-Origin Resource Sharing (CORS) request using the CORS protocol [FETCH], 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.

    + +

    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 solid:proxy 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.

    + +

    Additionally, using a proxy allows applications to mask their Origin, 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.

    +
    +
    +
    -

    7. Other predicates

    +

    8. Other predicates

    A user, a server or an application with appropriate permissions can add From 58d527f68723cd1b6da3dcb0c36d29b8e71b1c58 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Sun, 13 Oct 2024 12:32:49 +0200 Subject: [PATCH 2/2] Clarify proxy usage evaluation --- index.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/index.html b/index.html index b6e3f66..c9f6ec8 100644 --- a/index.html +++ b/index.html @@ -1292,6 +1292,8 @@

    7. Proxy

    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 solid:proxy 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.

    Additionally, using a proxy allows applications to mask their Origin, 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.

    + +

    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.