Explicitly set the content-type on HTTPReceiver responses to the /slack/install route #1280
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.
Summary
While most browsers will automatically infer the content-type header even if not set on HTTP responses, certain cloud hosting systems (e.g. AWS API Gateway) integrate with a variety of other services to provide content and have no means of inferring the content type. As a result, deploying bolt apps to AWS and integrating with API Gateway can be difficult.
This PR explicitly sets the Content-Type header to
text/html
for HTTPReceiver/slack/install
route responses.This PR fixes #1279.