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.

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

gateway: CDN-Loop #426

Open
lidel opened this issue Jul 11, 2023 · 0 comments
Open

gateway: CDN-Loop #426

lidel opened this issue Jul 11, 2023 · 0 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@lidel
Copy link
Member

lidel commented Jul 11, 2023

Problem

  • ipfs.io backed by saturn looping to itself
  • saturn looping to itself to the same L1 and always failing due to gaulty L1 and the internal ring hashing
  • any two gateway operators multiplexing on top of each other

Solution

Find and document a way for gateway operators and CDNs to avoid loops.

Prior Art

CDN-Loop seems to be the best candidate?

Ref.

Example

Request that was sent to ipfs.io, then hit saturn backend, and then hit one of Saturn L1s would have:

CDN-Loop: saturn-l1-id, saturn.tech; ipfs.io;  

This allows:

  1. ipfs.io to detect and drop requests that loop to itself
  2. saturn to either detect drop requests that loop to itself or route request to a DIFFERENT L1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant