https://bugs.winehq.org/show_bug.cgi?id=53792
--- Comment #2 from Jakub Staroń kubastaron@hotmail.com --- (In reply to Rafał Mużyło from comment #1)
Correct me if I'm wrong, but the way I understand it, that particular winhttp.dll is an injection proxy.
Yes it is an injection proxy but whats wrong with that? Windows allows it without any registry hacks so why wouldn't wine? I can understand wine intercepting the load of system libraries from system directories but why would it do it for libraries in the application directory? Doorstop works by (ab)using the fact that Windows will load winhttp.dll from the current directory instead the system one, but then it loads the real winhttp.dll from C:\windows\system32, so why couldn't wine intercept just the real one?