-
Notifications
You must be signed in to change notification settings - Fork 3
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
Provide "LDConfigSetProxyURI" in the 3.x client-side C/C++ SDK #426
Comments
Hi @ngangomsamananda , you filed this issue earlier: #394 Was the workaround I provided not sufficient, or has the requirements changed? |
@cwaldren-ld the requirements have changed. Could you take up this on priority? We are stuck in the upgrade process. Thanks. |
Ok, what are the new requirements? Why does the previous workaround no longer work? |
The workaround |
Is it SOCKS4 or SOCKS5 or both? I will file a feature request, but I cannot promise any timeline. |
Hi @cwaldren-ld I got know to we need to support all kinds of proxy currently available in the world including HTTP/HTTPS and SOCKS. In the old version (v2.5.2) |
We need the same feature of |
Hi @cwaldren-ld, do you have idea how long this might take to complete? I am asking this only because if we know rough estimates we can plan the SDK upgrade accordingly. |
Hi @ngangomsamananda , I do not have an estimate. I can raise this internally. Please send me an email at |
Is your feature request related to a problem? Please describe.
We are stuck on the end-of-life LDSDK v2.5.2 because "LDConfigSetProxyURI" is not available in the v3.x client-side C/C++ SDK.
Describe the solution you'd like
Support for LDConfigSetProxyURI in the v3.x client-side C/C++ SDK for connecting to LaunchDarkly through a web proxy.
Describe alternatives you've considered
We upgraded to v3.5.0 but found the functionality missing.
We confirmed in the LDSDK documentation that this feature is available in the client-side C++ SDK's version 2.x only. It is not yet available in version 3.0.
Additional context
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: