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

Shouldn't dag api take paths, not just CIDs? #3500

Closed
jbenet opened this issue Dec 13, 2016 · 0 comments · Fixed by #3517
Closed

Shouldn't dag api take paths, not just CIDs? #3500

jbenet opened this issue Dec 13, 2016 · 0 comments · Fixed by #3517
Assignees
Labels
help wanted Seeking public contribution on this issue
Milestone

Comments

@jbenet
Copy link
Member

jbenet commented Dec 13, 2016

Version information:

> ipfs version --all
go-ipfs version: 0.4.5-dev-4cb236c
Repo version: 4
System version: amd64/darwin
Golang version: go1.7

Type:

This should work

http://127.0.0.1:5001/api/v0/dag/get?arg=/ipfs/QmYNmQKp6SuaVrpgWRsPTgCQCnpxUYGq76YEKBXuj2N4H6

I get

{"Message":"selected encoding not supported","Code":0}

and

http://127.0.0.1:5001/api/v0/dag/get?arg=QmYNmQKp6SuaVrpgWRsPTgCQCnpxUYGq76YEKBXuj2N4H6

works fine :/

@whyrusleeping whyrusleeping added this to the ipfs 0.4.5 milestone Dec 15, 2016
@whyrusleeping whyrusleeping added the help wanted Seeking public contribution on this issue label Dec 15, 2016
@whyrusleeping whyrusleeping self-assigned this Dec 15, 2016
@whyrusleeping whyrusleeping added the status/in-progress In progress label Dec 17, 2016
@whyrusleeping whyrusleeping removed the status/in-progress In progress label Dec 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Seeking public contribution on this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants