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
Working on a hosting cluster with many public interfaces and multiples services, I want to be able to deploy this project with other similar projects under a shared subdomain. Each project would be assigned a subpath (for example, "https://services.example.com/links").
With the latest 1.13 release, deploying this project behind a reverse proxy causes the project to fail as all links are hardcoded to the root of the project.
Currently, the project does not take into account paths provided by the "X-Forwarded-*" headers and would greatly improve the various environments this will get deployed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Working on a hosting cluster with many public interfaces and multiples services, I want to be able to deploy this project with other similar projects under a shared subdomain. Each project would be assigned a subpath (for example, "https://services.example.com/links").
With the latest 1.13 release, deploying this project behind a reverse proxy causes the project to fail as all links are hardcoded to the root of the project.
Currently, the project does not take into account paths provided by the "X-Forwarded-*" headers and would greatly improve the various environments this will get deployed.
Beta Was this translation helpful? Give feedback.
All reactions