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.

Sign up for GitHub

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

Jump to bottom

error=\"invalid_token\" in response headers: NSS v5.6.8 #1

Open

crspybits opened this issue Sep 5, 2021 · 0 comments

Member

crspybits commented Sep 5, 2021 •

edited

Loading

I'm getting this but it doesn't cause a failure. I have this comment in createAuthenticationHeaders:

I thought initially, I should append a "/" to the htu because I was getting the following in the http response (despite having a 200 status code):

AnyHashable("Www-Authenticate"): "Bearer realm="https://inrupt.net\", error="invalid_token", error_description="htu https://crspybits.inrupt.net/NewDirectory does not match https://crspybits.inrupt.net/NewDirectory/\""

But that response header doesn't always occur: nodeSolidServer/node-solid-server#1572 (comment)

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment