Welcome to the Consumer Data Right Support Portal

Check out our guides, browse through our FAQs, and post your own questions for Support.

New to the Consumer Data Right? Learn more

Query on Content Type and Accept Header Field


1 comment

  • Avatar
    Cuc Tran

    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?

    Comment actions Permalink

Please sign in to leave a comment.