express-http-proxy | Proxy middleware for express/connect | Runtime Evironment library

I've my site built on node + express, and trying to enable gzip compression using this tutorial but it didn't worked as shown in the tutorial. I can't see Content-Encoding in response header.

Here is my code.

I am building a proxy service that will forward all but one kind of a POST request to another server.
I was planning on using express-http-proxy to do this but I can't find a way to modify the POST request on the fly.
For Example:

I want to catch all POST requests to /getdata and check if they have a field called username,
if they do I want to replace it with a custom username and then forward the request to another server and then forward the response from it back to the user.

Any help is appreciated. Any package or resource would help. Thanks.

I have a server hosting my app plus a few microservices (all of them are very simple web apps). I would like to access these services through the internet but without opening a port for each one. so I decided that I would set up a reverse proxy ( using express-http-proxy) on the server so that I can access all the services through a single port. the problem is that while I can access the main page of each service, all the relative links point to incorrect locations.

here is an example:

service.js

After update to angular 9 and universal 9, a got error when i run npm run build:ssr && npm run serve:ssr

I have a UI set up for users to select tests. Once they choose, I want to start a test runner with the 'remote' browser and give the user the URL so that they can watch the tests perform live in their browser.

In Heroku, there is no way to access non-standard ports. I attempted to use express-http-proxy so that I could create a route to where TestCafe was running on localhost. I was unable to get the proxy to work for TestCafe (though it did work for other pages).

To rule out issues with the proxy, I will be attempting to route to TestCafe by using nginx as soon as possible.

Is it even possible to run remote TestCafe tests behind a proxy?

In other words, I want to point example.com/remotetest to the TestCafe runner at localhost:3789 and watch a test run.