Someone invoked #curl on Windows powershell, saw a problem and reported it to us.

Yes. It was the dreaded alias. Again. Not a problem in "the real curl". I tried to get rid of this sorry thing, remember?

daniel.haxx.se/blog/2016/08/19…

#curl
in reply to daniel:// stenberg://

@FlippoFlip That is even worse then... so they have the real curl preinstalled but still invoke that slow and annoying piece of trash called Invoke-WebRequest. What's their reason for not just using a wrapper around curl that preserves Invoke-WebRequests interface and allows for curl options. Do they track usage of I-WR for monetization?
in reply to daniel:// stenberg://

What kind of idiot would alias to a command that doesn't support the same argument syntax as the alias name??

Oh dang, i now see this is Microsoft we're dealing with.. Okay in their defence they're REALLY bad at computer, nobody in the company ever took a comp sci course, so it isn't their fault.

And their users are equally dumb if using windows for big boy / big girl tasks. It's fine to ignore them when their curl alias "got broke", nothing can save them. Let them have the alias.

⇧