4 ms·
The Windows provided curl is not for user consumption IIRC. If any application is using it, that’s a bug.
by colejohnson66 3y ago
The Windows provided curl is not for user consumption IIRC. If any application is using it, that’s a bug.
- ugexe 3y agoDo you have any evidence of this? IIRC it is completely expected for users to consume it — https://learn.microsoft.com/en-us/virtualization/community/team-blog/2017/20171219-tar-and-curl-come-to-windows https://learn.microsoft.com/en-us/virtualization/community/t...
- myfonj 3y agoFrom what I recall from aforementioned incident, I was not able to reliably prove that client app (Eclipse) really used Windows' curl (I would have guessed that such software would have it's own internal stack for network connections, but my knowledge in this area is non-existent), only that it exhibited suspiciously similar problems. So I came to conclusion that it either uses that CURL or CURL that is similarly broken as the Windows' one. I was unable (or more precisely haven't even tried) to swap Windows curl with the "better" one to see if it fixes Eclipse Maven. Result back then was only that HTTP2 was disabled on the Maven server and all (windows) clients (both of them) were happy. (Other might become less happy since it presumably slowed something down.)