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

Include ability to download any content type via gateway port. #5436

Closed
andrewheadricke opened this issue Sep 7, 2018 · 1 comment · Fixed by #5437
Closed

Include ability to download any content type via gateway port. #5436

andrewheadricke opened this issue Sep 7, 2018 · 1 comment · Fixed by #5437
Assignees
Labels
topic/docs-ipfs Topic docs-ipfs

Comments

@andrewheadricke
Copy link

andrewheadricke commented Sep 7, 2018

Enhancement request:

There are lots of public IPFS gateways for read-only access to content uploaded in file format.. But it is not possible to access any other content like DAGs, custom objects, blocks etc from public gateways.

This means there is an incentive NOT to adopt any other formats apart from standard the standard file object, as its the only data accessible from public gateways.

If I could fetch DAGs, objects, blocks etc from public gateways, still read-only, then I would be inclined to use the newer DAG formats etc.

Stebalien added a commit that referenced this issue Sep 7, 2018
fixes #5436

License: MIT
Signed-off-by: Steven Allen <[email protected]>
@ghost ghost assigned Stebalien Sep 7, 2018
@ghost ghost added the status/in-progress In progress label Sep 7, 2018
@Stebalien
Copy link
Member

The gateway does, in fact, expose a read-only API (a subset of the normal API). I've just added some (very basic) documentation in #5437.

@Stebalien Stebalien added the topic/docs-ipfs Topic docs-ipfs label Sep 7, 2018
@ghost ghost removed the status/in-progress In progress label Sep 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic/docs-ipfs Topic docs-ipfs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants