Reputation: 6216
I have a function app which works as expected for https.
Someone in my organisation created a link to it, but forgot the "s" in https... the result is a redirect (supplied by the function app) to https://my-function-app.azurewebsites.net/ms-ext-routing/v1 (the "ms-ext-routing" portion is added by the function app, it seems - the "v1" is part of the original url)
This yields a 404.
I've tried creating a separate function to intercept this unknown url and redirect back to the https version of the app, with no success.
So, what is this redirect and how can I fix it / compensate? (other than the obvious option of getting people to link to the correct protocol - which is in process as I write this)
Upvotes: 2
Views: 3174
Reputation: 314
The function app should have Azure Functions Proxies enabled and a route defined as /v1. Look for the proxies.json file in the root of your function app.
If proxies are not needed you can disable them in the portal.
Upvotes: 0