I have a spec app.yml
that I use to setup a service and a frontend in the App platform (I trimmed down the yaml file):
name: airmeeple
static_sites:
- name: frontend
source_dir: frontend
routes:
- path: /
services:
- name: backend
source_dir: backend
routes:
- path: /api
When DO re-routes requests to the backend, it strips the prefix /api
such that if the request service.com/api/user
, the service will receive the request /user
.
Is it possible to configure the reverse proxy such that the prefix is kept when rerouting the request, such that the service sees a request with the path /api/user
?
Thanks in advance!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
@yehudi @mirkul This was added by DO, there is now a
preserve_path_prefix
when configuring a route that allows the prefix to be kept.Hey @Longwelwind,
it looks like our backend infrastructure is currently going to rewrite the host to “/” when making a routeable upstream for all services. I hear you about wanting to retain the path. I think when our team first built this, they expected that you would want to have your application route for itself, but I think your suggestion is totally valid. Currently, we always rewrite the host for apps, but I’ll see about implementing this customization.
Same here