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
In order to proxy URLs that encode key parameter details as part of the domain, we need better built-in support for multiple domains or wildcard domains.
Environment
Local development, wherein the "multiple URL" nature leans on the implicit "wildcarding" provided by Outrigger DNSDock. For example, api.projectname.vm, fr.api.rojectname.vm, de.api.projectname.vm will all be routed to the same container.
Required Actions
Populated X-Forwarded-Host with the Request Domain
Provide instructions on how to get variable domains registered in the X-Forwarded-Host header so the upstream can examine the downstream request host, embedded with key request parameters.
Preferred: nginx-only (Not Working)
In our target environment context, the "wildcard DNS" approach works but I have not found how to populate the X-Forwarded-Host header with the full request domain, it is reduced to the actual DNS entry. nginx proxy requests are sent with an Origin header that includes the correct domain.
Fallback: nginx & docker-compose (Working)
nginx.conf.tmpl: Replace X-Forwarded-Host configuration of {{ getenv "PROXY_DOMAIN"}} with $host. In this way the forwarded host should use whatever reaches it. (This was not sufficient for the nginx-only approach above.)
docker-compose.yml: Add com.dnsdock.aliases, with comma-delimited entries for each variant domain
Goal
In order to proxy URLs that encode key parameter details as part of the domain, we need better built-in support for multiple domains or wildcard domains.
Environment
Local development, wherein the "multiple URL" nature leans on the implicit "wildcarding" provided by Outrigger DNSDock. For example, api.projectname.vm, fr.api.rojectname.vm, de.api.projectname.vm will all be routed to the same container.
Required Actions
Populated X-Forwarded-Host with the Request Domain
Provide instructions on how to get variable domains registered in the X-Forwarded-Host header so the upstream can examine the downstream request host, embedded with key request parameters.
Preferred: nginx-only (Not Working)
In our target environment context, the "wildcard DNS" approach works but I have not found how to populate the X-Forwarded-Host header with the full request domain, it is reduced to the actual DNS entry. nginx proxy requests are sent with an Origin header that includes the correct domain.
Fallback: nginx & docker-compose (Working)
nginx.conf.tmpl: Replace X-Forwarded-Host configuration of
{{ getenv "PROXY_DOMAIN"}}
with$host
. In this way the forwarded host should use whatever reaches it. (This was not sufficient for the nginx-only approach above.)docker-compose.yml: Add com.dnsdock.aliases, with comma-delimited entries for each variant domain
Wildcard/Multi-domain CSR Certificate
Still researching.
The text was updated successfully, but these errors were encountered: