-
Notifications
You must be signed in to change notification settings - Fork 246
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
Different Responses with different Accept Headers #218
Comments
Hello @solidnerd , yes we have never really defined if the "default" response of the Universal Resolver should be just the DID document, or the DID resolution result (DID document + metadata). Sorry if this broke something, maybe we should have communicated this beforehand. Are you maybe available to discuss this on the next Universal Resolver Work Item Call (Wednesday 7pm CEST)? If you want to get just the DID document, I think the safest thing should be to explicitly request the official media type of the DID document representation, e.g. for the JSON-LD representation:
|
@peacekeeper Sadly next week I can't attend since we have a lot of internal stuff to do. But the Week afterwards seems to be fine from my side. There we can discuss it. |
@solidnerd Okay sounds good, let's discuss then. We have these Universal Resolver Work Item Calls every week. |
Related issue: #150 |
Hey,
we stumbled across a breaking change and want to ask if this is intended. Currently when you don't set the
Accept
Header to
*/*
we get different results back from the uni-resolver.Example with * / *
Example with application/json
The text was updated successfully, but these errors were encountered: