Hello there!
I’ve noticed today that GPT4 extensions/chat/completions endpoint returns 400 Request body validation error for charset=utf-8.
Content-Type: application/json; charset=utf-8.
This worked fine until today and still works fine on GPT3 endpoints.
Is this a bug or from now on, charset should not be sent?
Thanks for your response, I’m aware of existing documentation.
My question still stands.
The charset parameter is an optional part of the Content-Type header, and it specifies the character encoding used for the content. Character encoding determines how characters and symbols are represented as binary data in the response.