IIS Configuration Fix for Nodejs app (Fix an issue with hosting Nodejs apps on windows server)

Job ID: 38916219

Budget: $10 – $30 CAD

I'm experiencing issues with my Angular (Frontend) and Strapi (Backend) application hosted on a Windows Server using IIS as a reverse proxy. The application sometimes returns a 502 Bad Gateway error instead of the expected 206 Partial Content response.

The flow of events is as follows:
1. A file request is made by the browser (Frontend app).
2. The request is forwarded to the Backend (Strapi) by IIS.
3. A 206 Partial Content response is returned by the Backend.
4. Instead of receiving this response, IIS sends a 502 Bad Gateway error to the client.
5. The browser is forced to retry the same file request.

This issue arises from the fact that IIS, which is primarily designed for hosting .Net applications, is being used with a Node.js application.

I'm looking for an expert who can:
- Diagnose and fix the IIS configuration.
- Tweak request forwarding rules, response handling and proxy settings.
- Potentially help with setting up a more suitable hosting environment if necessary.

You should have extensive experience with IIS configuration, as well as a good understanding of Node.js applications. Please apply if you are confident in your ability to resolve this issue.
Related categories: Software Architecture IIS Azure Windows Server Node.js