Closed Flixt closed 1 month ago
We encountered a problem when a client made an OPTIONS request, because committee does only validate the content type header for POST, PUT and PATCH requests.
OPTIONS
POST
PUT
PATCH
The OpenAPI (3) schema for the endpoint looks like this:
MySchema: type: object required: - document_id properties: document_id: type: integer
The client left out the Content-Type header and sent and empty request body which did not lead to an Committee::InvalidRequest error.
Content-Type
Committee::InvalidRequest
We encountered a problem when a client made an
OPTIONS
request, because committee does only validate the content type header forPOST
,PUT
andPATCH
requests.The OpenAPI (3) schema for the endpoint looks like this:
The client left out the
Content-Type
header and sent and empty request body which did not lead to anCommittee::InvalidRequest
error.