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
{{ message }}
This repository was archived by the owner on Jul 6, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 6, 2026. It is now read-only.
Handle case insensitivity when processing HTTP response headers for Autorest Java #1272
Cognitive Services recently enabled HTTP/2.0 in APIM. Unlike HTTP/1.1 which states that clients/servers should treat the headers in a case-insensitive way, HTTP/2.0 requires all headers to be in lower-case.
It breaks the current behavior, specifically for the Computer Vision Track 1 SDK since the client code (OkHTTP) directly uses the latest available HTTP protocol but does not process the response headers in a case insensitive way resulting in an NPE.
It would help if autorest java could handle the HTTP response headers in a case-insensitive manner.
Closing as the design for a while has been to consume HttpHeaders and pull them out using case-insensitive retrieval, rather than the old design that used a special Jackson ObjectMapper with case-insensitive property name matching.
Activity
srnagar commentedon Dec 1, 2021
Sameeksha Vaity (@samvaity) it would be great to document the bug noticed in Computer Vision and capture the gist of the discussion in this issue.
alzimmermsft commentedon Nov 6, 2025
Closing as the design for a while has been to consume
HttpHeadersand pull them out using case-insensitive retrieval, rather than the old design that used a special Jackson ObjectMapper with case-insensitive property name matching.