This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
End invalid Slack signature response. #1833
Merged
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
When the Slack adapter receives an invalid signature header, it sets the status code of the response to 401 but does not end the response. This causes requests to hang that do not have a valid signature. This commit therefore fixes the issue
|
This helps with #1835 |
benbrown
approved these changes
Oct 24, 2019
|
thanks! will be putting out another slack update soon. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When the Slack adapter receives an invalid signature header, it sets the status
code of the response to 401 but does not end the response.
This causes requests to hang that do not have a valid signature. This commit
therefore fixes the issue