Request proxying of custom HTTP headers
Steps to reproduce the issue, if applicable. Include the actual command and output and/or stack trace.
- Start http-server with the -P parameter pointing to a backend server that is reachable.
- Send a request, containing a custom HTTP header, to http-server that should be proxied to the configured server.
What did you expect to happen? I expect the custom HTTP header to be available in the request as it is received in the backend server.
If the issue is a feature request, what is the motivation / use case for it? I use http-server to run a development version of my Angular web application. The application needs data from a REST endpoint that requires a custom HTTP header to be present.
Tell us about your environment
- **exact http-server version:**0.12.3
- **Node version:**8.10.0
- **Platform:**Windows 10
👍
Another scenario is to set proxy headers such as "X-Forwarded-For" / "X-Forwarded-Proto" ... to give the back end server hints about the public URL.
This issue has been inactive for 180 days
I'd consider this a breach of the principle of least astonishment, request headers should be forwarded
This issue has been inactive for 180 days