Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: hostname matching in proxies #1987

Open
StephenCleary opened this issue Oct 3, 2017 · 3 comments
Open

Feature request: hostname matching in proxies #1987

StephenCleary opened this issue Oct 3, 2017 · 3 comments
Assignees
Milestone

Comments

@StephenCleary
Copy link

It would be great if we could include host matching in the matchCondition of proxies.json, e.g.:

{
    "$schema": "http://json.schemastore.org/proxies",
    "proxies": {
        "static": {
            "matchCondition": {
                "host": "www\\.example\\.com",
                "route": "{*url}"
            },
            "backendUri": "https://%STATIC_HOST%/"
        }
    }
}

so the proxy would be triggered by https://www.example.com/some/url, but not https://api.example.com/api/some/function/call.

(periods in the hostname are escaped in this example because I'm assuming the match would be a regex).

@lazytesting
Copy link

Would be awesome to have this possibility on every header. By example, for a soapservice I would like to be able to route the traffic based on the SoapAction header.

@prabhakarreddy1234
Copy link

Any update on this feature release timelines ?

@Misiu
Copy link

Misiu commented Jan 4, 2023

That would be a great addition!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants