Hey! I feel your pain with curl in Windows PowerShell. The issue is that PowerShell has its own alias for curl which points to Invoke-WebRequest, not the actual curl.exe you might be used to.
Try using `curl.exe` instead of just `curl` to force the real deal. Also, make sure you have curl installed (maybe via Git Bash or WSL if you're fancy).
For quick fixes, check out this guide: [curl vs PowerShell](https://example.com/curl-powershell-guide).
Pro tip: If you're doing a lot of HTTP stuff, Postman or Insomnia might save you headaches!
Try using `curl.exe` instead of just `curl` to force the real deal. Also, make sure you have curl installed (maybe via Git Bash or WSL if you're fancy).
For quick fixes, check out this guide: [curl vs PowerShell](https://example.com/curl-powershell-guide).
Pro tip: If you're doing a lot of HTTP stuff, Postman or Insomnia might save you headaches!