Query on Content Type and Accept Header Field
Hi Team,
We have the queries as given below related to Content Type and Accept Header Field
- Content Type:
1) What are the Valid Content Type Header Values, and should we consider only the references given in non-normative example as the only valid values?
Content-Type: application/json;charset=UTF-8 Content-Type: application/json Content-Type: AppliCAtion/JSon;Charset=uTf-8
2) If the Content Type Header exist but the values as given above is not part of the Incoming request, should the request be rejected and if so, what is the Error Response Code (406 Not Acceptable or 400 Bad Request-Invalid Header)
- Accept Header:
1) What are the Valid Accept Header Values, and should we consider only the references given in non-normative example as the only valid values as given below?
Accept: */* Accept: application/json;charset=UTF-8 Accept: application/json Accept-Encoding: charset=UTF-8 Accept: AppliCAtion/JSon;Charset=uTf-8
2) Should the Request be rejected if the Accept Encoding Header value is not as given above with 406 Error Response?
-
Nils Berge and Jarryd looking for your support on this ticket urgently. We recently implemented a fix from our end to validate the incoming header accept-encoding and return 406 if the incoming value is not charset=UTF-8 as per the non-normative examples in the standard.
However, all the requests from the ADRs related to Customer and Direct Debit endpoints are failing with 406 as the incoming Accept-Encoding header value is not charset = UTF-8.
Urgently seeking your guidance if we should roll-back this fix from our end to allow 200 response first. Or if we should keep the fix as it is compliant with the standard and raise separate cases to the ADR to fix from their end?
Please sign in to leave a comment.
Comments
1 comment