Ensure the /slack/install
oauth installation handler sets the content-type in its HTTP response
#1279
Closed
1 task done
Labels
bug
M-T: confirmed bug report. Issues are confirmed when the reproduction steps are documented
Milestone
Description
This was filed internally at Slack, but, if you look at this code, the default HTTPReceiver OAuth installation handler response explicitly does not set a
Content-Type
HTTP response header. While most browsers can deal with this automatically, some hosting providers (like AWS' API Gateway) does not.Suggestion: we set the content-type header explicitly in this area of the code.
What type of issue is this? (place an
x
in one of the[ ]
)The text was updated successfully, but these errors were encountered: