We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
I have the following webhook config:
I redacted the real url/path of course 😉
But in the log I saw:
[telegram bot] Webhook enabled: {"url":"https://sub.myhost//path/wh/telegram/1943XXX","has_custom_certificate":false,"pending_update_count":0,"max_connections":40,"ip_address":"XX.XX.XX.XXX"}
Also redacted the token and IP.
And so, Telegram sends me webhook on this url (with double slash between host and path) which was not the wanted one (https://sub.myhost/path/wh/telegram/1943XXX)
I had to add a new HAProxy acl:
acl acl_webhook_telegram path_beg //path/wh/telegram/
This behavior is quite new, I think it was introduced in 16.1.1 or 16.1.2
The text was updated successfully, but these errors were encountered:
@nioc thanks for reporting... this is obviously not the intention... I will fix it asap
Sorry, something went wrong.
9bd6d1a
#402
765e90e
No branches or pull requests
Hello,
I have the following webhook config:
I redacted the real url/path of course 😉
But in the log I saw:
Also redacted the token and IP.
And so, Telegram sends me webhook on this url (with double slash between host and path) which was not the wanted one (https://sub.myhost/path/wh/telegram/1943XXX)
I had to add a new HAProxy acl:
This behavior is quite new, I think it was introduced in 16.1.1 or 16.1.2
The text was updated successfully, but these errors were encountered: