-
Notifications
You must be signed in to change notification settings - Fork 284
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 support for outbound SSL w/ SSL1.1.x #1981
Fix support for outbound SSL w/ SSL1.1.x #1981
Conversation
Without this patch, there are compilation errors with undefined references when trying to seen HTTPS connections when using OpenSSL1.1.x. You can duplicate this issue by trying `requestHTTP("https://google.com").toString.writeln;`
Is this actually a fix against master/0.8.2-rc.1 or against 0.8.1? The mangling of both signatures should be the same, so it's currently still unclear to me why this would fix a linker error. 0.8.1 on the other hand had these functions defined as aliases, which indeed resulted in unresolved symbol errors. |
I see the same failure signature for both 0.8.2 and 0.8.2-rc.1 |
Hm, interesting. Can you post the error message? It would be interesting to know what exactly differs from the linker's point of view (I don't have a Fedora installation available ATM, so I can't reproduce it). Thanks for the fix. Hopefully this will finally get all current systems to work (and not break some other system). In the long run we should set up a Docker based Fedora/CentOS test on Travis-CI to better catch these distribution specific differences. |
Using 0.8.1-rc.1 (locally tagged master as 0.8.2):
using 0.8.1:
|
There are some undefined symbols, such as |
You are absolutely correct. That was my mistake. Here are the correct errors: w/ 0.8.1
w/ 0.8.2-rc.1
With this patch, the request succeeds. |
Ah, okay, that makes sense. Maybe it's simply DMD that didn't catch it. |
Without this patch, there are compilation errors with undefined
references when trying to seen HTTPS connections when using
OpenSSL1.1.x. You can duplicate this issue by trying
requestHTTP("https://google.com").toString.writeln;
I've seen this issue occur and be fixed with this patch on both
Fedora 26 and 27.