Align HTTP APIs and the documentation

[hsanjuan]

We are going to take js-ipfs current HTTP API definition as source of truth.

I will go through all endpoints and check that they are aligned in go-ipfs, otherwise submit issues for inconsistencies.

The apiary docs need to reflect js-ipfs http API as well, to the point that it is possible to autogenerate tests from them.

Actionable items:

• Submit issues to go-ipfs about missaligned endpoints
• Fix HTTP API related issues in go-ipfs
• Fix apiary http-api docs Fix Apiary spec and align it with js-ipfs API ipfs-inactive/http-api-spec#122
• Create automated tests from apiary docs

Planned deadline: Week 5, November 15th, 2016

[daviddias]

Let's take this to the thread on http-api-spec.ng - Roadmap, Priorities and Discussions of where to take the HTTP API

[Mr0grog]

@diasdavid that repo is archived, so nobody can comment there. Maybe ipfs-inactive/http-api-docs#3 is better? (That’s the repo it was archived in favor of, I think.)