Dweb.link now redirects to inbrowser.link

Help
1

I noticed while testing that dweb.link now redirects to inbrowser.link. I understand that it was not realistic to expect the free protocol labs public gateways to work indefinitely, but just wanted to mention, I hope all are aware that the helia client is still very broken, (at least, on chrome based browsers, download some html headers instead of file contents, and it looks like ipns is not working at all today.)

Edit: IPNS got fixed :slight_smile:

2

What issues were / are you experiencing?

As for the saving issue you described, what were you doing? It seems like you might be running into "Save as" broken: saves SW bootstrap HTML instead of IPFS data · Issue #574 · ipfs/service-worker-gateway · GitHub which is a chrome bug Chromium that we are working with Igalia and the Chromium team to fix.

In the meanwhile, clicking the download button at the top of the page should help if you navigated directly to a jpeg, video, etc.

3

I had been using the dweb.link proxy for a few demos and tools. The switch to inbrowser.link broke 3 of them for 2 reasons:

  • .mjs files are now served with a Content-Type: application/octet-stream HTTP header, so loading them as native es module fails because of strict mime type checking as per HTML spec.
  • The Service Worker Gateway uses react-router-dom’s HashRouter. One of my apps uses the URL hash value for routing too, so initializing it with a route will now let the Service Worker Gateway grab the route and abort loading with a “No routes matched location” error. Example: https://<my-cid>.ipfs.inbrowser.link/#/mail/Inbox results in “No routes matched location ‘/mail/Inbox’” error.

I know .mjs isn’t required for es modules and I’ve fixed the issue by renaming all es modules to .js. Still, it would be nice if a mime type could be added for .mjs.

I don’t know how to fix the routing issue though. Any ideas?

The Service Worker Gateway, verified-fetch and the push for more decentralization is really great, thanks for putting all the hard work in! Most of my apps have been using their own service worker which I can remove now :slight_smile:

4

@ccmm thank you for reporting issues. :folded_hands:

Small ask: in the future please fill them directly in Issues · ipfs/service-worker-gateway · GitHub, it will make it easier for the team to triage.
To illustrate, I filled separate issue for every problem you described:

5

Will do! Thank you very much!