Nikk8091 commented on issue #12918: URL: https://github.com/apache/seatunnel/issues/12918#issuecomment-6297867642
Hi, I'd like to work on this charset follow-up if it is still available. I inspected `BaseServlet.requestBody()` on dev at `1ce2d7815665`: it calls `getReader()` before converting the resulting string to UTF-8. I also checked #12921, whose description explicitly leaves this charset behavior out of scope, and found no separate charset-fix PR in the current search. My proposed scope is to centralize UTF-8 decoding when no charset is declared, preserve explicitly declared valid charsets, and cover unsupported charsets with a clear client error. I would add real-server regressions for non-ASCII HOCON/SQL/JSON on `/submit-job` and JSON on `/submit-jobs`, including absent and explicit charset cases, and check the REST documentation. The query/form-parameter fix would stay in #12921. I see the reporter has offered to submit a fix, so could you confirm whether they are already preparing this follow-up or whether I can take it? I will wait for confirmation to avoid duplicate work. Thank you! -- 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]
