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

Allow access to the content from within the /.well-known/ directory. #31

Closed
alrra opened this issue Jun 2, 2014 · 0 comments
Closed

Comments

@alrra
Copy link
Member

alrra commented Jun 2, 2014

From https://www.mnot.net/blog/2010/04/07/well-known:

One of the nagging theoretical problems in the Web architecture has been finding so-called “site-wide metadata”; i.e., finding something out about a Web site before you access it. We wrestled with this in P3P way back when, and the TAG took it up after that.

The easy solution to this is to define a static “well-known” URL — like /robots.txt. However, having a third party come along and squat on part of every Web site’s URL namespace is less than friendly, and eventually it’ll lead to conflicts.

So, in a less-than-ideal but practical solution, RFC5785 now defines a sandbox for these well-known URIs — /.well-known/, and provides a registry for them to assure that they won’t conflict.

See also: http://tools.ietf.org/html/rfc5785

@alrra alrra self-assigned this Jun 2, 2014
@alrra alrra changed the title Allow access to the /.well-known/ hidden directory Allow access to the content from within the /.well-known/ directory. Jun 2, 2014
@alrra alrra closed this as completed in 04785b7 Jun 2, 2014
@alrra alrra removed their assignment Jun 2, 2014
Cryszon added a commit to Cryszon/server-configs-nginx that referenced this issue Jun 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant