Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix that curl generates a SIGPIPE that causes application to exit due to upstream device killing idle TCP connection #2906

Merged
merged 11 commits into from
Oct 20, 2024

Conversation

abraunegg
Copy link
Owner

  • 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
* Add forced HTTP/1.1 downgrade based on bad curl versions usually found in Ubuntu distributions
@abraunegg abraunegg changed the title Add triage for #2874 Fix that curl generates a SIGPIPE that causes application to exit due to upstream device killing idle TCP connection Oct 20, 2024
* Add node regarding 'Could not connect to server on handle'
* Test curl version only if 'force_http_11' is false
* Make stale curl idle value a config option
* reorder ?
* Update PR
@abraunegg abraunegg merged commit 2e93c1f into master Oct 20, 2024
1 check passed
@abraunegg abraunegg deleted the fix-issue-2874 branch October 22, 2024 04:30
@abraunegg
Copy link
Owner Author

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Repository owner locked and limited conversation to collaborators Oct 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant