This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 14.000000000000002%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERJ%3C/text%3E%3C/svg%3E)
Hi,
We are using Azure Web App for many years and for the last 4 we have used httpplatformhandler to pass requests to our nodejs processes (the handler was more stable than iisnode which has some quirks). Everything worked smoothly in Azure App Service v. 99.0.7.671.
The currently in progress deployment of version 99.0.10.774 breaks something as the nodejs worker processes are restarting every minute or two (no incoming request is coming thru). We haven't changed anything in the app. There was even a situation when new version was available only on one instance of web app and old on the other and only the new one were restarting. We were forced to switch to iisnode in web.config to have the website running again properly.
We have prepared minimal nodejs web app using httpplatformhandler and we can reproduce the issue. Below are two versions with exact minimal code, one works one does not:
https://bint-nodetest.azurewebsites.net/ does not work and has version99.0.10.774.
https://bint-nodetest2.azurewebsites.net/ works and has version 99.0.7.671.
Does anyone have similar issues as we cannot find anyone talking about this breaking the web app update.
Regards,
Rafal
Hmm, interesting. We think we have found the cause of this. Nodejs app started by just binding to a port and without setting the hostname, as it always worked before. It looks with new version it must be set directly to 'localhost' to allow httpplatformhandler to connect. Mayby this was a part of the security bugfix or something like that but very suprising to guess what to change when suddently everything no longer works especially when nodejs itself says port was opened without error on listen() callback.
@Rafał Jońca I'll touch basis with the team and let you know what I find out.
Thank you,
Before the update simple .listen(process.env.PORT, (err) => ...); worked (we are using httpplatformhandler for over 4 years). After the update you have to do .listen(process.env.PORT, 'localhost', (err) => ...); to get everything working. Maybe there was a security patch implemented or something similar but documentation on httpplatformhandler does not mention binding exactly to localhost so it was not easy to find a fix.
@Rafał Jońca let's continue your issue offline. Please respond to the private message down below.
Hi @Rafał Jońca ,
Per our offline discussions, you informed me that the ANT 99.0.10.790 does appear to have resolved the issue. I do have an incident open to investigate the root cause of this issue. When I receive any findings, I'll update this post.