-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PLU-370: [CUSTOM-API-FIX-2] do not overwrite Content-Type #823
PLU-370: [CUSTOM-API-FIX-2] do not overwrite Content-Type #823
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Datadog ReportBranch report: ✅ 0 Failed, 722 Passed, 0 Skipped, 2m 13.08s Total Time |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm tested that fix works thks
Merge activity
|
6992e34
to
f9ccec2
Compare
TL;DR
Updated Custom API header handling to ensure:
Content-Type = application/json
, if not set by userContent-Type
set in Connection step is not overwritten byContent-Type
set in Custom HeadersWhat changed?
Content-Type
header is now set for all requests toapplication/json
instead of Axios' defaultapplication/x-www-form-urlencoded
How to test?
Content-Type
setContent-Type
header is present and isapplication/json
Content-Type
Content-Type
header is present and matches what was setContent-Type
to Custom header stepContent-Type
set in the Add connection stepWhy make this change?
The Content-Type header should be set consistently for all requests. The previous implementation only set it for requests with headers specified in the Connection step.