jscheffl opened a new pull request, #59676: URL: https://github.com/apache/airflow/pull/59676
After we deployed Airflow 3.1.5 to our environment @AutomationDev85 and me noticed that still the WAF rules hit the deployment and debugging one level deeper revealed a logic problem of the fix applied in #57377: The call from base class `patch()` to the extended `Client` from TaskSDK uses actually (empty) kwargs for content and header (e.g. passing `content=None` and `header=None` which then made the header not applied. See also https://github.com/encode/httpx/blob/master/httpx/_client.py#L1221 This PR corrects the logic to check for "if any content is to be submitted" and "No header for content type set". With this the content-type header is now consistently applied making our WAF happy. -- 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]
