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

[crspybits]

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)