You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I can tell, Windows 11 or the batch file are converting your curl request to Invoke-WebRequest as a command.
Similar situation here. Can you ensure that this is not the case for you?
@truthsword To build on their answer, you could do either:
Install regular curl, the easiest way to do it is to go to cURL website and download a binary, then Remove-Alias curl; curl <...> or use path\to\curl.exe <...>
Use the built-in web request facility in PowerShell. It should look something like this: Invoke-WebRequest "http://192.168.1.60:8070/message?token=njvrfrihrfr" -Method POST -Form @{ title = "some stuff here"; message = "hello!" }
Thank you, @BroderPeters and @eternal-flame-AD. I located curl.exe natively in C:\Windows\System32, so I used that full path (I thought about adding curl to the PATH environmental variable), so this worked:
I want to send a notification upon completion of a batch file running in Windows. I tacked on the following curl command to my batch file:
But it failed with this response:
This curl command works fine in Debian. What's the trick with Win11? Thanks!
The text was updated successfully, but these errors were encountered: