We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the current specs we have the following non normative example
POST /request HTTP/1.1 Host: client.example.org Content-Type: application/x-www-form-urlencoded wallet_metadata=%7B%22vp_formats_supported%22%3A%7B%22jwt_vc_json%22%3A%7B%22alg_values_supported %22%3A%5B%22ES256K%22%2C%22ES384%22%5D%7D%2C%22jwt_vp_json%22%3A%7B%22alg_values_supported%22%3A% 5B%22ES256K%22%2C%22EdDSA%22%5D%7D%7D%7D& wallet_nonce=qPmxiNFCR3QTm19POc8u
This is compliant to the following sentence, we have in the Section 5.11. Request URI Method post
The request MUST use the HTTP POST method with the https scheme, and the content type application/x-www-form-urlencoded
Is there any pratical reason to not use application/json and then have the following solution?
application/json
POST /request HTTP/1.1 Host: client.example.org Content-Type: application/json { "wallet_metadata" : {"vp_formats_supported":{"jwt_vc_json":{"alg_values_supported":["ES256K","ES384"]},"jwt_vp_json":{"alg_values_supported":["ES256K","EdDSA"]}}}, "wallet_nonce": "qPmxiNFCR3QTm19POc8u" }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In the current specs we have the following non normative example
This is compliant to the following sentence, we have in the Section 5.11. Request URI Method post
Is there any pratical reason to not use
application/json
and then have the following solution?The text was updated successfully, but these errors were encountered: