You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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
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).
The text was updated successfully, but these errors were encountered: