DanielLeens commented on issue #12918: URL: https://github.com/apache/seatunnel/issues/12918#issuecomment-6340368560
Thanks for avoiding a parallel patch while the ownership was unclear. Classification: A / Zeta REST API request-body charset. I rechecked current `dev` and the open PR set: #12921 explicitly leaves this charset behavior out of scope, and there is no separate charset implementation PR linked from the reporter. You may take this focused follow-up; the issue is now assigned to you for tracking. @fatmanverse, if you already have an implementation branch, please link it immediately so the work can be consolidated rather than duplicated. Please keep the change centralized in `BaseServlet#requestBody` and audit every v2 servlet that uses that method, not only `/submit-job` and `/submit-jobs`. When no request charset is declared, decode as UTF-8; continue honoring a valid explicit charset and return a clear client error for an unsupported declaration. Add real-server REST coverage for non-ASCII bodies with and without an explicit charset, including the relevant JSON and HOCON/text endpoints, and document the contract in the v2 REST API documentation. Do not fold this into #12921's query-parameter/body-order fix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
