DanielLeens commented on issue #12918: URL: https://github.com/apache/seatunnel/issues/12918#issuecomment-6290742651
Classification: A / Zeta REST request-body character decoding. The source path is credible: `BaseServlet.requestBody()` first uses the servlet reader and only then encodes the resulting Java string as UTF-8. Once an undeclared-charset body has been decoded with the servlet default, that final UTF-8 conversion cannot recover the original non-ASCII bytes. #12921 intentionally fixes the form-parameter consumption issue only, so it must not be expanded to include this separate contract. Please open a focused follow-up that centralizes the body-decoding rule for all affected REST endpoints. An absent charset should use UTF-8 for SeaTunnel HOCON/SQL/JSON input; an explicitly declared valid charset must either be honored consistently or rejected with a clear client error. Add real-server tests for non-ASCII HOCON, SQL, and JSON bodies with and without a charset, including `/submit-job` and `/submit-jobs`. Keep it separate from #12921 so both fixes remain reviewable. -- 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]
