This repository has been archived by the owner on Jan 7, 2018. It is now read-only.
Add ability to have wildcard backend hostnames #15
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.
This extends the wildcard hostname support added in #13 Now the backend host can be rewritten to also contain the matched piece of the wildcard in the frontend host (previously the backend host was either static or an empty string, in which case the frontend host was passed through verbatim).
The backend host just uses the same wildcard
*
syntax for the replacement value. Now with a frontend host like*.example.com
and a backend host of*.api-backend.foo
, a request topenguin.example.com
would be rewritten intopenguin.api-backend.foo
.