-
Notifications
You must be signed in to change notification settings - Fork 232
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
IPIP-351: IPNS Signed Records Response Format on HTTP Gateways #351
Conversation
b6a3e2e
to
2d8eded
Compare
It's ready for review! Implementation too. |
9874e89
to
8d55e97
Compare
|
||
## Detailed design | ||
|
||
The solution is to allow the Gateway to provide an IPNS signed record by |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should Gateway be capitalized as it is here? (It's lowercase in other places on this doc)
7d4d566
to
98a41f1
Compare
@lidel I just rebased and cleaned up this PR. |
http-gateways/PATH_GATEWAY.md
Outdated
@@ -188,6 +188,7 @@ For example: | |||
- [application/vnd.ipld.dag-cbor](https://www.iana.org/assignments/media-types/application/vnd.ipld.dag-cbor) – requests [IPLD Data Model](https://ipld.io/docs/data-model/) representation serialized into [DAG-CBOR format](https://ipld.io/docs/codecs/known/dag-cbor/). If the requested CID already has `dag-cbor` (0x71) codec, data is validated as DAG-CBOR before being returned as-is. Invalid DAG-CBON produces HTTP Error 500. | |||
- [application/json](https://www.iana.org/assignments/media-types/application/json) – same as `application/vnd.ipld.dag-json`, unless the CID's codec already is `json` (0x0200). Then, the raw JSON block can be returned as-is without any conversion. | |||
- [application/cbor](https://www.iana.org/assignments/media-types/application/cbor) – same as `application/vnd.ipld.dag-cbor`, unless the CID's codec already is `cbor` (0x51). Then, the raw CBOR block can be returned as-is without any conversion. | |||
- [application/vnd.ipfs.ipns-record](https://www.iana.org/assignments/media-types/application/vnd.ipfs.ipns-record) – requests a verifiable [IPNS Record](../ipns/IPNS.md#ipns-record) to be returned. Produces 400 Bad Request if the content is not under the IPNS namespace, or contains a path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💭 need to register before merging
c2d9055
to
7ce972e
Compare
5e34d7b
to
fddaa93
Compare
From @lidel: Will try to take care of IANA things this week and either way can merge by the end of the week (5/12/23) |
c2a4779
to
b36ccf1
Compare
b36ccf1
to
1ac8ecb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This IPIP got ratified before Kubo 0.19, but we had no time to finalize editorials.
Pushed final tweaks, and references to text fixtures/asserts implementers could follow.
Merging. IANA submission will be tracked in ipfs/in-web-browsers#209
Closes #320.
Checklist
application/vnd.ipfs.ipns-record
with IANA (@lidel)ipns-record
code to the table (Add IPNS Record code multiformats/multicodec#312) and mention it in the spec so people don't useipns
namespace one