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
No HTTPS #966
Comments
It looks like wine's secur32 isn't compatible with native wininet/winhttp. You could try native secur32, but than that crashes: Native sspicli avoids the crash, but doesn't allow for working https, fyi. |
So who do I contact about fixing this as it worked several months ago but now after updating it does not? |
As a first step, you'd need to find what broke it (winetricks or wine). As a general rule, upstream wine is unlikely to consider wine's iexplore not working with native dlls a bug though. |
Using |
@JonnyTech I ran 'winetricks -q wininet winhttp' as you did, saw the problem, then tried 'winetricks -q secur32' since that was where the error was reported. I then tried iexplore again, which crashed. I extracted sspicli from win7sp1, manually placed it in system32 and overrode to native, but was still unable to load https sites. |
Are there upstream bugs for the wininet / winhttp problems? I couldn't find them in a quick search. |
The solution I found that fixes |
Cool. I'd still love to see an upstream bug filed for the metatrader problem. Feel free to CC me on it. |
As it affects multiple applications, is it not a Can you point me where to file an upstream bug report please? |
It's a wine issue. Please report to https://bugs.winehq.org, include the terminal output without any native overrides. Also include what winetricks commands help, to help narrow down the bug. |
Wine bug filed here: https://bugs.winehq.org/show_bug.cgi?id=44990 |
Running a 32 bit wine prefix on Debian:
Latest
winhttp
andwininet
installed from latestwinetricks
:But I cannot load in any
https
pages (http
only sites work fine)Files seem to be in the correct location:
What am I doing wrong?
The text was updated successfully, but these errors were encountered: