-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Use .well-known
path for assets to avoid conflicts
#3234
Comments
Sounds great! Are you open to send in a PR? |
Potentially, I just don't know the full extent of the usage of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
I was reading this blog post about assets and noticed that y'all were using
/avo-assets
. While it is extremely unlikely to conflict with anything, it is a possibility.Proposition
To solve this, I think it would make sense to use a
.well-known
path, as defined in RFC 86150 which are designed for exactly this purpose: to define a pathname for well-known resources that won't conflict with the webmaster's path namespace. Additionally, these can be registered with IANA to further prevent conflicts.The text was updated successfully, but these errors were encountered: