Forwarding through reverse proxy for non-static files #130
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Thank you for your contribution. This ended up being a duplicate of #134. In the future conforming to the project code style is a big 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have added support for basic reverse proxy. The way it works is if file is not found by ecstatic, it will fall back to forwarding the request to a proxy server, configured by -f parameter, for .e.g http-server -f http://localhost:5000/ etc. This is very basic support to keep in line with spirit of http-server to keep it simple and cli driven.
We are using this as small replacement of nginx in dev environment. So that static files can be served as well as it works as reverse proxy for rest of the requests.