IIS reverse proxy issue for Nodejs web app
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.
I need a professional with experience in diagnosing and fixing IIS configurations for Node.js applications specifically.
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.
The issue arises from the fact that IIS, which is primarily designed for hosting .Net applications, is being used with a Node.js application.
I need a professional with experience in diagnosing and fixing IIS configurations for Node.js applications specifically.
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.
The issue arises from the fact that IIS, which is primarily designed for hosting .Net applications, is being used with a Node.js application.