* Craig A. Berry <craig.a.berry@gmail.com> [2021-12-10 16:22:27 -0600]: > On Fri, Dec 10, 2021 at 3:59 PM Martijn Lievaart <m@rtij.nl> wrote: > > > > > > Op 10-12-2021 om 22:30 schreef Craig A. Berry: > > > > [1] https://docs.microsoft.com/en-us/windows/win32/api/wininet/nf-wininet-internetreadfile > > > > > > From that page: > > > > Note WinINet does not support server implementations. In addition, it should not be used from a service. For server implementations or services use Microsoft Windows HTTP Services (WinHTTP). > > > > If that means Windows Server implementations do not support this API, then another one should probably be used. But surely there is one that works on all types of Windows OS? > > Thanks, but I think that just means you can't implement services with > it. We don't want to implement an http(s) service, just an http(s) > client, even if it's running on a server version of Windows. I see this thread is still dragging on. Was the idea of documenting how to get it going on the most common systems using their native package systems dismissed conclusively dismissed as an idea? Beyond that, the only one that made any sense to me was, "try to install Net::SSLeay, but if it fails clean up the mess and move on". Frankly, this is not upstream perl's problem to solve; but efforts can be made to make it an easy "next step" - unless there are cases where it absolutely must be in place? I haven't read the latest 95% of this thread so maybe this was provided? Cheers, Brett -- -- oodler@cpan.org oodler577@sdf-eu.org SDF-EU Public Access UNIX System - http://sdfeu.org irc.perl.org #openmp #pdl #nativeThread Previous | Thread Next