Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Microsoft Teams webhook fails after certificate creation (reason: empty payload)
See original GitHub issueDescribe the bug Microsoft Teams webhook fails after certificate creation with error:
Failed invoke webhook. Status Code = BadRequest, Reason = Invalid webhook request - Empty Payload
To Reproduce Steps to reproduce the behavior:
- Follow setup instructions and configure a Microsoft Teams webhook.
- Create a new certificate.
- Search the application insights for “webhook”.
- See webhook error that occurred after certificate creation.
Environment (please complete the following information):
- Certificate Type: Zone Apex and www
- Certificate Deploy Target: Front Door
Additional context
I noticed that Teams recently changed the format of their webhook URL. It now has the format: https://xxx.webhook.office.com/webhookb2/xxx/IncomingWebhook/xxx/xxx. Previously it was: https://outlook.office.com/webhook/xxx/IncomingWebhook/xxx/xxx. I checked the source code for this project which seems to be looking for .office.com, so I don’t believe the URL format change would negatively impact webhook execution.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This issue has been fixed in
v3.6.6. Thank you!Thank you. I was able to identify the cause.
It seems that Incoming Webhook in Teams does not handle requests with
Transfer-Encodingcorrectly. I’m working on a fix to avoid this problem now.