Marcin Rataj
Marcin Rataj
Ref. https://bugs.chromium.org/p/chromium/issues/detail?id=1473980 > > ## What steps will reproduce the problem? > > 1. Visit https://helia-identify.on.fleek.co/ > 2. Open the console > 3. Wait a minute or two > >...
> Update 2023Q2: this spec was known as "Private Network Access", got [renamed](https://github.com/WICG/local-network-access/issues/91) to "Local Network Access" since then. Explainer: https://github.com/WICG/cors-rfc1918/blob/master/explainer.md https://wicg.github.io/private-network-access/ → https://wicg.github.io/local-network-access https://web.dev/cors-rfc1918-feedback/ https://groups.google.com/a/chromium.org/g/blink-dev/c/cPiRNjFoCag https://lists.webkit.org/pipermail/webkit-dev/2021-May/031836.html https://chromestatus.com/feature/5436853517811712 ## Summary...
> This issue tracks ideas, use cases and work related to [Web Packaging](https://github.com/WICG/webpackage/blob/master/explainer.md), especially [Signed HTTP Exchanges (SXGs)](https://github.com/WICG/webpackage/blob/master/explainer.md#signed-http-exchanges) and [Bundled HTTP Exchanges](https://github.com/WICG/webpackage/blob/master/explainer.md#bundled-exchanges) which open the door to associating an origin...
> This a placeholder for gathering references to create a more fleshed out plan. We have distinct Gateway (/ipfs, /ipns) and API (/api/v0) endpoints today, and only the most basic...
HTTP Gateway does content-type sniffing based on [golang.org/src/net/http/sniff.go](https://golang.org/src/net/http/sniff.go) and file extension. js-ipfs uses similar setup. **Problem:** there is no mechanism for website creator to override returned content-type, setting custom file...
> We have `ipfs://` and `ipns://` **URI** registered at IANA (https://github.com/ipfs/in-web-browsers/issues/29#issuecomment-629016191) already! > This issue is about **URN**, preferably scoped to CIDs without pathing. ### Why should we care? Semantic...
This is a stub/meta issue for tracking work to leverage Service Workers (SW) as a fallback on public gateways. > cc historical SW threads for discovery: #57 https://github.com/ipfs/in-web-browsers/issues/171 https://github.com/ipfs/in-web-browsers/issues/158 https://github.com/ipfs/kubo/issues/4025...
> This issue tracks what needs to happen before we enable WebRTC transport in JS-IPFS by default. It also acts as an entry point to existing resources in other repos....
## Motivation Websites loaded via path gateway are able to access cookies and storage of the entire domain. While we are moving to [subdomain gateways](https://docs-beta.ipfs.io/how-to/address-ipfs-on-web/#subdomain-gateway) (#89), requests made to path...
## Current state - Specifications for HTTP Gateways exist now at [ipfs/specs/http-gateways](https://github.com/ipfs/specs/blob/main/http-gateways) - For historical reasons, comprehensive, ent-to-end HTTP Gateway tests live in Kubo IPFS implementation (`*gateway*.sh` in [kubo/test/sharness](https://github.com/ipfs/go-ipfs/tree/master/test/sharness)) -...