Change Output header Content-Type to text/csv #175
Merged
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.
Introduction
Currently,
Output#output
expects to render a CSV file, but does not set the correct Content-Type header.Proposal
Describe the new/upated/fixed feature
Per RFC 7111, the content type is available
text/csv
.Further, HTTP 1.1 7.2.1 states
octet-stream
should only be used when the content-type is uknown.Output#output
sets Content-Type astext/csv
Backward Incompatible Changes
None
Targeted release version
8.1.1
PR Impact
None observed
Open issues
None