Example 08 - simple HTTP listener errors out with "Invalid Hostname" on port 9000 about burnttoast HOT 2 CLOSED

Looks like this is a quirk in either Invoke-RestMethod or the underlying .NET stuff.

The example as written does work. The listener is configured to listen to "localhost:9000", so if you run Invoke-RestMethod -Method Post -Body ($Body | ConvertTo-Json) -Uri "http://localhost:9000/" you will get a notification.

As soon as you try to call that listener locally using anything other than localhost, it seems like the HttpListener doesn't know how to handle it. I'm not actually sure if this setup work at all over the network?

It should be noted that these examples are community provided and meant as "huh, that's cool" type snippets intended to spark ideas of how this module could be used with some more fleshing out.

If this is a use case you're wanting to pursue, I'd highly recommend looking into something that's more production ready as an "API endpoint" than having a constant HttpListener running (Maybe PowerShell Universal or Polaris, though that one is unsupported.)

from burnttoast.

Many thanks - the issue was a missing http config in Windows 10 allowing external traffic.

The call is similar to

netsh http>add urlacl url=http://+:9000/toast/ user=BUILTIN\Users listen=yes
URL reservation successfully added

where the url entered in netsh must exactly match that of the registered listener in powershell. Thanks to https://www.msxfaq.de/code/powershell/pshttpserver.htm for the hints on what to change (page is in German).

from burnttoast.