Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
HTTP bindings for deactivated DIDs are ignored
See original GitHub issueHi,
While improving on the KILT did driver we realised that the current implementation of the universal resolver for the biggest part follows the did resolution specs on http bindings, but it seems to disregard the recommendation to flag deactivated DIDs with a 410 status code. We are wondering if that is intentional or whether it is worth fixing?
Examples
This way the deactivated status is obvious because of the document metadata:
curl -v https://dev.uniresolver.io/1.0/identifiers/did:kilt:4r6RdVMNes2eEobxyxH7aVsesUqR2X175sUAXJfo7dEWxHUS
Requesting only the document, however, obscures this (here the status code could help):
curl -v -H 'accept: application/did+ld+json' https://dev.uniresolver.io/1.0/identifiers/did:kilt:4r6RdVMNes2eEobxyxH7aVsesUqR2X175sUAXJfo7dEWxHUS
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@rflechtner thanks for pointing this out. I think I just fixed this in 35bb7af, could you perhaps verify on your end?
@cihanss I think we also talked about this.
Yes, I agree. The implementation is to spec now, so no issue here. The issue that the http binding is potentially error-prone would belong there. What do you think about the resolver UI handling 410’s differently though?