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.

Sign up for GitHub

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

Jump to bottom

http-api: Global API Issues #211

Open

3 tasks

RichardLitt opened this issue Feb 26, 2016 · 0 comments

Labels

Member

RichardLitt commented Feb 26, 2016

There are seemingly arbitrary differences in error messages that respond as a string, and those which respond with a JSON object with Message and Code. CF Error Messages: What does Code mean? kubo#2293
protobuf doesn't work as an encoding sometimes. The usage seems arbitrary and inconsistent.
xml isn't specified as a possible encoding, and encoding isn't specified as an option in most of the commands, although it is in some.

The text was updated successfully, but these errors were encountered:

daviddias changed the title ~~Global API Issues~~ http-api: Global API Issues

daviddias transferred this issue from ipfs-inactive/http-api-spec

daviddias added the topic/http-api label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment