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

Missing Timeout Configuration and SSL Connection Issue with MITM Proxy in WinHttpTransport and CurlTransport #6380

Open
Justsvetoslavov opened this issue Jan 29, 2025 · 0 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@Justsvetoslavov
Copy link

Issue Summary

No Callback Method for Timeout Settings
Neither WinHttpTransport nor CurlTransport have a callback method that allows us to set up additional settings.

Timeout Support in WinHttpTransportOptions & CurlTransportOptions

WinHttpTransportOptions does not support either connection or data timeouts, while CurlTransportOptions at least supports a connection timeout, though it does not offer a way to configure a data timeout.

SSL Connection Error with MITM Proxy

We are experiencing an issue with CurlTransport when using HTTP/HTTPS proxy through a Man-in-the-Middle (MITM) proxy for testing. The connection consistently fails with an "SSL connection error."

Request for Assistance

We would appreciate assistance with understanding whether we are missing any configuration or if there's a recommended workaround for these issues. Is there a way to handle timeouts more effectively, and how can we resolve the SSL connection error when using a MITM proxy, through the CurlTransport class? Any guidance or suggestions would be greatly appreciated!

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

1 participant