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
Currently the deployment router at the edge will use the value of the Host: header to decide where to route requests and by default will only accept my-project-name.shuttleapp.rs. This is not ideal for self-deployments which are not deployed as a subdomain of shuttleapp.rs.
We could expose a parameter in Shuttle.toml which lets users configure a Host key for their deployment.
The text was updated successfully, but these errors were encountered:
Currently the deployment router at the edge will use the value of the
Host:
header to decide where to route requests and by default will only acceptmy-project-name.shuttleapp.rs
. This is not ideal for self-deployments which are not deployed as a subdomain ofshuttleapp.rs
.We could expose a parameter in
Shuttle.toml
which lets users configure aHost
key for their deployment.The text was updated successfully, but these errors were encountered: