Attempt to catch internal 500 responses#11
Open
jesusbagpuss wants to merge 1 commit intozimeon:masterfrom
Open
Attempt to catch internal 500 responses#11jesusbagpuss wants to merge 1 commit intozimeon:masterfrom
jesusbagpuss wants to merge 1 commit intozimeon:masterfrom
Conversation
From reports on Google group, Nov. 2021 where the external server may not actually be receiving the request, possibly due to issues in the SSL connection process (mis-matched TLS versions; no shared ciphers etc.).
Owner
|
Many thanks for this @jesusbagpuss , I'm not ignoring it but afraid have been swamped recently... |
Author
|
I know how that feels 😁 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
NB I haven't got a sensible way to test this change - please treat with caution.
From reports on Google group, Nov. 2021 where the external server may not actually be receiving the request, possibly due to issues in the SSL connection process (mis-matched TLS versions; no shared ciphers etc.).