Add Content-Type to Request Header in Task SDK calls #57377
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jscheffl
added
the
backport-to-v3-1-test
potiuk
approved these changes
Oct 27, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Oct 27, 2025
) (cherry picked from commit 8695fc5) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
Backport successfully created: v3-1-test
|
github-actions bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Oct 27, 2025
…che#57377) (cherry picked from commit 8695fc5) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We deployed Airflow3 today first time together with Edge Worker in our environment. (I know way too late, but still now getting started...)
We received HTTP 403 from the client as our WAF rejected calls with POST/PATH w/o appropriate content-type sent with the request.
Whereas technically not needed and we know how communication runs between client and server, we needed to add an exception to make remote deployment via Edge possible.
Therefore I'd suggest - even if technically not needed - to add a proper content-type to request header if a body is sent This will lower trouble in other deployments hard to debug on WAF and especially in security hardened environment.