Support for the Content-Type request header. #15
Conversation
This file contains 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
Added -type option for Content-Type with default.
When load-testing with POST requests, the server often cares what the content
type is, i.e it needs a Content-Type header in the request. This change adds
the option to set that explicitly with the -type flag, which you might use
for testing raw JSON payloads as well as file uploads; and a sane default if
there is POST data to send:
Content-Type: application/x-www-form-urlencoded
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi there! I was trying out gobench and my target server was rejecting POST requests due to a bad Content-Type request header. This was trivial to fix so I forked and added that support. Please consider merging this in, as I am sure there are others who would need this feature.