search

lbussy / brew-bubbles

It beats watching the grass grow!
https://www.brewbubbles.com
Other
18 stars 5 forks source link

Path for URL Target not being extracted correctly #49

Open ChrisThomas42 opened 1 year ago

ChrisThomas42 commented 1 year ago

Using a path for URL general target does appear to be extracted correctly. The path to my target includes a port, the IP address appears to be OK but the PORT reported is 80 rather than the one in my path. If I use the same path and POST from RESTer then the target receives the data correctly.

URL Target: http://IP:8123/api/webhook/brewbubbles1

Telnet Output: 2023-01-31T14:57:28Z V: Triggered URL Target push. 2023-01-31T14:57:28Z V: Host lookup: 192.168.20.145. 2023-01-31T14:57:28Z V: Resolved host 192.168.20.145 to IP 192.168.20.145. 2023-01-31T14:57:28Z N: Posting to: 192.168.20.145 2023-01-31T14:57:28Z V: Connecting to: 192.168.20.145 at 192.168.20.145 on port 80 2023-01-31T14:57:28Z W: Connection failed, Host: 192.168.20.145, Port: 80 (Err: 0) 2023-01-31T14:57:28Z E: URL Target post failed.

I hope that's sufficient information?

Levi--G commented 1 week ago

Found the same issue today, is there a workaround possible in the mean time?