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
Although header keys are to be treaded as case-insensitive according to RFC2616 many server implementations will still compare header keys in a case sensitive way, especially with authorization headers
Even in official documents like RFC6750 the Authorization header is written in uppercase.
As there is no real need for this library to enforce HTTP headers beeing lowercase, I would propose to remove the conversation and simply take the header key as it is stored in the schema
The text was updated successfully, but these errors were encountered:
The function
SecurityScheme.createAuthorizationHeader
always converts the header key of the authorization schema to lowercasehar-sdk/packages/oas/src/converter/security/schemas/SecuritySchema.ts
Lines 37 to 40 in baae5b4
Although header keys are to be treaded as case-insensitive according to RFC2616 many server implementations will still compare header keys in a case sensitive way, especially with authorization headers
Even in official documents like RFC6750 the
Authorization
header is written in uppercase.As there is no real need for this library to enforce HTTP headers beeing lowercase, I would propose to remove the conversation and simply take the header key as it is stored in the schema
The text was updated successfully, but these errors were encountered: