Alberne commented on PR #9497: URL: https://github.com/apache/seatunnel/pull/9497#issuecomment-3043304060
> Hi @Alberne . I found this issue already fixed by #9363. Could you verify it again? We should set request header by user themself now. Yes, I suggest making adjustments to the original logic for compatibility. The initial logic was that the system automatically adds the Content-Type header, so it should first check whether the user has already set the Content-Type header. If the user hasn't customized it, the system should then set it. Additionally, because the original logic automatically adds the Content-Type header, the tasks currently running in production have not custom-set this header. If we do not perform compatibility checks, it would affect the online tasks. -- 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]
