Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path for URL Target not being extracted correctly #49

Open
ChrisThomas42 opened this issue Jan 31, 2023 · 0 comments
Open

Path for URL Target not being extracted correctly #49

ChrisThomas42 opened this issue Jan 31, 2023 · 0 comments
Labels
bug Something isn't working upstream Issue with core or a supporting library.

Comments

@ChrisThomas42
Copy link

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?

@lbussy lbussy added bug Something isn't working upstream Issue with core or a supporting library. labels Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream Issue with core or a supporting library.
Projects
None yet
Development

No branches or pull requests

2 participants