Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature request: fallback path when backend returns 404 #606
I heavily use Azure Functions proxies to serve single page applications stored in a Blob Storage container. However, when those applications use push state-based routing, deep linking doesn't work by default because the web server is expected not to return a 404, but to fall back to
At the moment, I end up copy & pasting the same function acting as proxy with this fallback mechanism in all of my apps. It would be pretty neat if Azure Functions proxies supported this.
@safihamid sure :)
Today my code acts just like a proxy. The only difference is that, if the backend returns a 404, my function
The new feature I'd like to see is being able to specify fallback paths per HTTP status code for a given proxy. The proxy would then follow this algorithm:
This would allow to use proxies not only to handle deep linking for single page applications, but also to support different response overriding scenarios such as custom error pages.