Webhook subscription is triggering with no body

Supporting both transfer-encoding: chunked and content-length headers is correct and required. This is because the header is switched dynamically depending on the size of the content.

For some users, the issue might be caused by apache server. So no matter how you change your code, it simply doesn't work. You may need to update your apache server or change to nginx.

Ref: https://bz.apache.org/bugzilla/show_bug.cgi?id=63366

It looks like they rolled back the update, our Logic App is working again now.

Hi Developers,

I just want to let you know that we just rolled back the previous HTTP library which supports the content-length header. This roll-back is necessary and will be just a temporary solution for a certain period of time (about 30 days) so that developers would have enough time to prepare and update their web server that supports the transfer-encoding: chunked header.

For those who already successfully updated to newer web server that supports the transfer-encoding: chunked header should keep using that new web server since it should support both headers.

We will send out an official announcement with better information related to the change and timeline.

We apologize for any inconvenience this may have caused you due to this unintentional break.

@Phong Vu Is there any planned support for developers that use Azure Logic Apps to monitor RingCentral Webhooks? Azure support has reviewed the chunked header issue with us and said, "that is more of a limitation that won't be fixed anytime soon. There were internal discussions happening about this issue, but I think the fix is proving harder to do than expected. For now we just ask as a work around that the content length be set in the header when using chunking." Will this workaround be possible to implement?

Hi Iain et all,

I just had a discussion with the engineering team and the decision is that we will change the config to keep using the content-length header. So we will not roll back to use transfer-encoding: chunked anymore.

However, there is one remaining thing for us to decide is to add the body with some default content to the validation token post, the very first post that we send a validation-token header and the client app has to echo back the validation-token in the response header, in order to successfully create the webhook subscription. The reason we would add some content to the body is to keep the content-length header and set it to the length of the body content instead of content-length: 0.

I will announce when the final decision is made but you can assure to keep your code as it is right now.

I don't think there is any problem sending a Content-Length: 0 header if the body is empty. It had not been a problem prior to the change to chunked encoding. It is probably even okay to not send a Content-Length header at all if there is no content body. It was only a problem when there was no Content-Length header and there _was_ content to read.