Headers properties should be case insensitive.

HTTP Header names are case insensitive. Swagger specification enforce to be case sensitive all field names without exceptions.

All field names in the specification are case sensitive.

Parameter names are case sensitive.

The specification should clarify headers names are case insensitive and must be validated in that way.

So the following schema:

"parameters": [
  {
    "name": "petId",
    "in": "heaer",
    "type": "string"
  }
]

"headers": {
  "X-Rate-Limit-Limit": {
    "description": "The number of allowed requests in the current period",
    "type": "integer"
  }
}

Should be validate these headers as valid headers:

headers: [
  "PETID",
  "x-rate-limit-limit"
]

[IndunilRathnayake]

Hi @jharmn,

Would like to know the conclusion of this discussion. We have the same concern where the java-library in [1] has been used, which is built based on the OpenAPI specification.

As per the Hypertext Transfer Protocol specification in [2] :

4.2 Message Headers
Field names are case-insensitive.

As per the OpenAPI specification v3.0 in [3] :

All field names in the specification are case sensitive. This includes all fields that are used as keys in a map, except where explicitly noted that keys are case insensitive.

header - Custom headers that are expected as part of the request. Note that RFC7230 states header names are case insensitive. 

So that the OpenAPI specification not expecting to validate header names, case-sensitively. Rather stating to validate case-insensitively. Please verify.

[1] https://bitbucket.org/atlassian/swagger-request-validator/src/swagger-request-validator-2.3.0/ [2] https://tools.ietf.org/html/rfc2616#section-4.2 [3] https://swagger.io/specification/

Thanks Indunil

[casualjim]

I think it should be spec’ed that headers need to be canonicalized. It should at the very least trigger a validation warning by the tools, consistently.