Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redirect to Default when no Vanity path is provided #464

Open
asthalonworks opened this issue Feb 17, 2023 · 2 comments · May be fixed by #502
Open

Redirect to Default when no Vanity path is provided #464

asthalonworks opened this issue Feb 17, 2023 · 2 comments · May be fixed by #502
Labels
enhancement New feature or request feature-request

Comments

@asthalonworks
Copy link

Currently when you visit the root domain (e.g. just the root domain https://shortenertool-12345-fa.azurewebsites.net), you are presented with the "Your Functions App is Up and Running" page.

The result of no path provided should be the same as a path provided that's not in the table - redirect to the default. When using a custom domain this can be achieved with a redirect rule, but it's not preferable.

This would help to obfuscate the underlying platform which is beneficial from a security standpoint.

Thanks!

@nmartin5
Copy link

@asthalonworks If your goal is only to hide the fact that you are using an Azure Functions App, you can disable the homepage. https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#azurewebjobsdisablehomepage

@FBoucher FBoucher added enhancement New feature or request feature-request labels Jun 16, 2023
@WhiteTomX WhiteTomX linked a pull request Jul 23, 2023 that will close this issue
@PatSunter
Copy link

+1 this would be a very useful feature for the URL shortener's usability.

Looks like there is already a linked PR that implements it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature-request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants