From b0c678683531d9f1aa51ea8d36c8af46f94d8dda Mon Sep 17 00:00:00 2001 From: bumblefudge Date: Fri, 27 Oct 2023 00:59:21 +0200 Subject: [PATCH 1/2] update native urls secn in ipfs in the browser --- docs/how-to/address-ipfs-on-web.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/how-to/address-ipfs-on-web.md b/docs/how-to/address-ipfs-on-web.md index d84ec25fc..dc0a7387f 100644 --- a/docs/how-to/address-ipfs-on-web.md +++ b/docs/how-to/address-ipfs-on-web.md @@ -222,12 +222,12 @@ An example is this website, [https://docs.ipfs.tech](https://docs.ipfs.tech). For a complete DNSLink guide, including tutorials, usage examples, and FAQs, see [dnslink.io](https://dnslink.io). ::: -## Native URLs +## IPFS-Scheme URLs -The native address format is the same as a [subdomain gateway](https://docs.ipfs.tech/how-to/address-ipfs-on-web/#subdomain-gateway) HTTP URL, but with two differences: +URLs that combine the "native" IPFS address format with an IPFS-specific scheme are structured in a way very similar to `http`/`https`-scheme URLs" that rely on a [subdomain gateway](https://docs.ipfs.tech/how-to/address-ipfs-on-web/#subdomain-gateway) for their location-based authority component. These were historically called "Native URLs" since they combine a native IPFS address with an IPFS-native scheme, but note the differences between a subdomain-gateway HTTP(S) URL and a IPFS-scheme URL: -- The protocol scheme is replaced by the `ipfs` or `ipns` namespace -- The location-based authority component (the gateway host and port) is replaced with a CID +- The `ipfs` or `ipns` protocol schemes are used for http, depending on the namespace (`ipns` is a subset of `ipfs`) +- The location-based authority component (the gateway host and port) is replaced with a bare, native CID ```plaintext ipfs://{cid}/path/to/subresource/cat.jpg From 7bcd7523f4752fecfbc337eabbc21a022895a0d9 Mon Sep 17 00:00:00 2001 From: Bumblefudge Date: Fri, 27 Oct 2023 01:06:21 +0200 Subject: [PATCH 2/2] clarity edit --- docs/how-to/address-ipfs-on-web.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to/address-ipfs-on-web.md b/docs/how-to/address-ipfs-on-web.md index dc0a7387f..e8b0389e0 100644 --- a/docs/how-to/address-ipfs-on-web.md +++ b/docs/how-to/address-ipfs-on-web.md @@ -226,7 +226,7 @@ For a complete DNSLink guide, including tutorials, usage examples, and FAQs, see URLs that combine the "native" IPFS address format with an IPFS-specific scheme are structured in a way very similar to `http`/`https`-scheme URLs" that rely on a [subdomain gateway](https://docs.ipfs.tech/how-to/address-ipfs-on-web/#subdomain-gateway) for their location-based authority component. These were historically called "Native URLs" since they combine a native IPFS address with an IPFS-native scheme, but note the differences between a subdomain-gateway HTTP(S) URL and a IPFS-scheme URL: -- The `ipfs` or `ipns` protocol schemes are used for http, depending on the namespace (`ipns` is a subset of `ipfs`) +- The `ipfs` or `ipns` protocol schemes are used instead of `http` - The location-based authority component (the gateway host and port) is replaced with a bare, native CID ```plaintext