By Evert Heylen
I have an App Spec containing a forwarding rule that looks like this:
ingress:
rules:
- component: {name: "api-container"}
match: {path: {prefix: "/api/v1"}}
This enables “path trimming” (which I like!), so if I navigate to /api/v1/foo the container will only see /foo. Now if my app returns a redirect to /bar, it will not be rewritten to /api/v1/bar, which breaks the abstraction of “path trimming”.
Is there a way to enable this?
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!
Hi there,
The easiest workaround is probably handling it in your app - make your redirects return the full path including /api/v1 prefix since your app knows it’s behind that route. Not the cleanest since it couples your app to the deployment config but it works.
Hope that this helps!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
