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

inbrowser.tld: investigate HTTP 301 to avoid double download #577

Open
lidel opened this issue Feb 13, 2025 · 0 comments
Open

inbrowser.tld: investigate HTTP 301 to avoid double download #577

lidel opened this issue Feb 13, 2025 · 0 comments

Comments

@lidel
Copy link
Member

lidel commented Feb 13, 2025

quick brain dump, something to evaluate

  • cid.ipfs.inbrowser.tld needs own SW and the same JS and CSS assets related to SW are fetched for the second time from subdomain
  • we use cloudflare CDN, which allows us to set up extra rules
  • idea for perf. optimization
    • if every subdomain needs to fetch cid.ipfs.inbrowser.tld/foo.js|css to initialize SW init , would it be possible to return HTTP redirect to inbrowser.tld/foo.js|css and avoid sending same bytes twice for every domain
    • caveat
      • it may be that sw.js NEEDS to be loaded from cid.ipfs.inbrowser.tld origin but perhaps it could be lean and everything else could share cache from inbrowser.tld/foo.js|css?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant