You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
At the same time as fixing this, it would also be really nice if the response headers for the Client Identifier Document could be validated. In particular, the content-type should be validated to ensure it is of type application/ld+json as opposed to something like an octet-stream.
jeswr
changed the title
Remove validation does not work
Remote validation does not work
Apr 1, 2023
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On the page https://solid-client-identifier-helper.vercel.app/validator copy/pasting the json contents to validate works; but trying to use the fetch and validate function against a remote url (e.g. https://query.linkeddatafragments.org/solid-client-id.jsonld) fails with
.
Looking at my network requests that action does a POST request to https://solid-client-identifier-helper.vercel.app/api/validate-remote-document?documentIri=https://query.linkeddatafragments.org/solid-client-id.jsonld with an empty payload and gets a 500 response code.
The text was updated successfully, but these errors were encountered: