Bug 1944522 - Add Content-Type header option in Harbormaster HTTP Build step #46
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.
Bug 1944522
This PR adds an option to the Harbormaster HTTP Build Step to send an extra
Content-Type
header.The current behaviour is preserved by default: no
Content-Type
header is sent.I was able to test these changes locally, querying my own machine through a public IP from the docker container.
Using a debug server, I logged the headers sent by Phabricator when triggering manually a build plan: