-
Notifications
You must be signed in to change notification settings - Fork 492
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
Support POST-only HTTP API #1429
Comments
ipfs-webui uses ipfs-redux-bundle v6.0.1 which depends on old js-ipfs-http-client v39.0.2 This is pretty bad news, as fixing it means we need to update HTTP client to the latest version ( I'll jump into this for an hour or two and re-evaluate if its more than that. Sidenote: While $ rg "ky.get" v39.0.2/src
src/cat.js
23: const res = await ky.get('cat', {
src/files-regular/refs.js
52: const res = await ky.get('refs', {
src/files-regular/get.js
39: const res = await ky.get('get', {
src/files-regular/refs-local.js
12: const res = await ky.get('refs/local', {
src/files-regular/ls.js
34: const res = await ky.get('ls', {
src/pubsub/peers.js
17: const { Strings } = await ky.get('pubsub/peers', {
src/pubsub/ls.js
9: const { Strings } = await ky.get('pubsub/ls', {
src/config/profiles/list.js
11: const res = await ky.get('config/profile/list', { I believe we should not invest time in fixing that – everyone should upgrade to async iterables version of JS API (js-ipfs-http-client >=41.x) |
ipfs/kubo#7097 will block `GET` commands on API port, switching everything to POST. This breaks Files screen in ipfs-webui as noted in ipfs/ipfs-webui#1429 ipfs-webui is using older version of js-ipfs-http-client, one before huge refactor into async iterables, which means switching to the latest version won't be a trivial task. For now, we just apply simple patch on top of ipfs-http-client v39.0.2 to ensure it sends commands as POST. Proper fix will land when ipfs-webui is refactored to work with ipfs-http-client >41.x Closes #1429
ipfs/kubo#7097 will block `GET` commands on API port, switching everything to POST. This breaks Files screen in ipfs-webui as noted in #1429 ipfs-webui is using older version of js-ipfs-http-client, one before huge refactor into async iterables, which means switching to the latest version won't be a trivial task. For now, we just apply simple patch on top of ipfs-http-client v39.0.2 to ensure it sends commands as POST. Proper fix will land when ipfs-webui is refactored to work with ipfs-http-client >41.x Closes #1429
* fix: support POST-only HTTP API ipfs/kubo#7097 will block `GET` commands on API port, switching everything to POST. This breaks Files screen in ipfs-webui as noted in #1429 ipfs-webui is using older version of js-ipfs-http-client, one before huge refactor into async iterables, which means switching to the latest version won't be a trivial task. For now, we just apply simple patch on top of ipfs-http-client v39.0.2 to ensure it sends commands as POST. Proper fix will land when ipfs-webui is refactored to work with ipfs-http-client >41.x Closes #1429 * docs: remove GET from CORS setup for API
PR at ipfs/kubo#7097 will block
GET
on/api/v0
on API port.Seems that we need to fix ipfs-webui and release a new version so mentioned PR can be merged.
cc @hsanjuan @Stebalien
Known problems
/api/v0/ls
seems to be sent asGET
:The text was updated successfully, but these errors were encountered: