Fix that curl generates a SIGPIPE that causes application to exit due to upstream device killing idle TCP connection #2906
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
Owner
abraunegg
commented
Oct 14, 2024
abraunegg
commented
- Add releaseTimestamp to track when a curlEngine was last used
- Add additional logging output for further debugging issue
* Add releaseTimestamp to track when a curlEngine was last used * Add additional logging output for further debugging issue
* Remove logging output that was erroneously left in
* Add missing colon
* Cleanup PR and remove additional output / logging used during the development of this PR
* Fix logging output
abraunegg
changed the title
* Add node regarding 'Could not connect to server on handle'
* Test curl version only if 'force_http_11' is false
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.