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
As noted in RFC2616, HTTP headers are supposed to be case-insensitive.
I've noticed that when getting a token from the /oauth2/token endpoint, the authorization header needs to be capitalised and not lower case. This is not standard HTTP behaviour.
The text was updated successfully, but these errors were encountered:
Hm, that is quite unlikely because we're not using anything custom-made, only regular Go-libraries which are RFC conform. Could you show a reproducible test case?
As noted in RFC2616, HTTP headers are supposed to be case-insensitive.
I've noticed that when getting a token from the
/oauth2/token
endpoint, theauthorization
header needs to be capitalised and not lower case. This is not standard HTTP behaviour.The text was updated successfully, but these errors were encountered: