Skip to content
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.

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

Account Information metadata cannot be resolved due to case-sensitive headers matching #192

Open
anikoloutsos opened this issue Jul 12, 2021 · 0 comments · May be fixed by #193
Open

Account Information metadata cannot be resolved due to case-sensitive headers matching #192

anikoloutsos opened this issue Jul 12, 2021 · 0 comments · May be fixed by #193

Comments

@anikoloutsos
Copy link

When matching headers on the basis of a prefix, the check performed is case sensitive. However according to rfc2616 the headers should be case-insensitive (see: https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2)

This results in the AccountInformation not containing metadata given that the header response starts with "x-account-meta-" instead of "X-Account-Meta-"

anikoloutsos pushed a commit to anikoloutsos/joss that referenced this issue Jul 12, 2021
- Added case-insensitive check to getResponseHeadersStartingWith method
- Added validation for null prefix
@anikoloutsos anikoloutsos linked a pull request Jul 12, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant