Timeline for Powershell: passing json string to curl
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2021 at 21:07 | comment | added | mklement0 | Good point, @MortenB - that is definitely a requirement in Windows PowerShell (PowerShell versions up to v5.1). By contrast, curl is no longer a built-in alias in PowerShell's cross-platform edition, PowerShell (Core) 7+, and does invoke curl.exe there. | |
| Mar 13, 2020 at 15:09 | comment | added | MortenB | If you call curl in powershell it is an alias for Invoke-WebRequest, and that is not what you want, you should use curl.exe. You can see all aliases with Get-Alias. | |
| Jul 14, 2014 at 21:14 | comment | added | KoenJ | That doesn't make any difference.. Note that the command works fine when invoked from the command line, so the issue is not in the arguments being passed; it has something to do with Powershell and escape characters.. | |
| Jul 14, 2014 at 21:02 | history | answered | David Pullar | CC BY-SA 3.0 |