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

Allow HTTP headers to define an environment (not only subdomains) #12

Open
santiagofn opened this issue May 15, 2018 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@santiagofn
Copy link

santiagofn commented May 15, 2018

It'll be really cool if we can use certain HTTP header fields as parameters to identify an environment, and then not be restricted to use only subdomains.
(Real life example: at my work, we use custom HTTP request headers to set beta/rc enviroments).

@santiagofn santiagofn changed the title Allow HTTP headers to define an enviroment (not only subdomains) Allow HTTP headers to define an environment (not only subdomains) May 15, 2018
@ylecuyer
Copy link
Owner

Good idea @santiagofn. This is doable I will work on it and come to you when it is done for some testing

@ylecuyer ylecuyer added the enhancement New feature or request label May 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants