Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature: Add `Open in Gateway`

See original GitHub issue

Is your feature request related to a problem? Please describe. In #1813, the user wants a feature which is showing the downloading progress in the WebUI. However, If users can download through the browser, they can get the download progress they want. So if we can add a new Button called Open in Gateway orOpen in Browser, it will be convenient.

Describe the solution you’d like Before: After:

Describe alternatives you’ve considered Or Add a Button to help users copy the gateway URL of a file.

Additional context We can use ipfs config Addresses.Gateway to get Gateway address.

Issue Analytics

State:
Created 2 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

lidelcommented, Jul 30, 2021

Notes from triage:

let’s not add another action, it will be confusing (proposed one is a duplicate of Share)
right now the Download button uses JS API and a blob: as a source
fix here is to switch to HTTP link at a local gateway
- single file would have /ipfs/{cid}?filename=foo&download=true to ensure proper `content-disposition
- a directory – tbd, either /api/v0/ or ?format=tar (whichever is available when this is tackled)
  - ideally, we would implement this when /ipfs/<cid>?filename=foo&format=tar is provided (https://github.com/ipfs/go-ipfs/issues/8234), but faking it with something like ``/api/v0/get/?arg=<cid>&archive=true&compress=true&filename=foo.tar.gz` could also work