Add details about HTTPS binding. #108
Conversation
peacekeeper
requested review from
dmitrizagidulin,
mccown,
ChristopherA and
danpape
as code owners
| query parameters in the <var>request HTTP(S) URL</var>.</li> | ||
| </ol> | ||
| <li>Initialize a <var>request HTTP(S) URL</var> with the <var><a>DID resolver</a> HTTP(S) endpoint</var>.</li> | ||
| <pre class="example nohighlight">https://dev.uniresolver.io/1.0/identifiers/</pre> |
There was a problem hiding this comment.
We'll want to use a made-up URL here.
There was a problem hiding this comment.
I agree. I created issue #109 to address this across the whole document.
|
This was discussed during the #did meeting on 09 January 2025. View the transcriptw3c/did-resolution#108markus_sabadello: That's about the HTTPS interface. We have sections about the algorithm, how to resolve a DID, how to reference a DID URL. wip: Markus, do you have some issues you want us to focus on? markus_sabadello: No specific ones. |
Co-authored-by: Will Abramson <[email protected]>
| <a>DID resolution</a> and/or <a>DID URL dereferencing</a> functions (including all | ||
| resolution/dereferencing options and metadata) via an HTTP(S) endpoint. See <a href="#resolver-architectures"></a>.</p> | ||
|
|
||
| <p>The HTTP(S) binding is a <a>remote binding</a>. It requires a known HTTP(S) URL where a remote |
There was a problem hiding this comment.
Wondering if we need to say that HTTPS can also be used locally. HTTPS does not mean always connecting to a remote DID resolver
This PR adds some details on how the HTTP(S) binding works, i.e. how the resolve() and dereference() functions can be invoked via an HTTP(S) endpoint, and how resolution options, metadata, status codes, etc. are handled.