內容簡介
這個外掛為 WordPress 啟用「知名 URI」的支援（RFC 5785: http://tools.ietf.org/html/rfc5785）。
從 RFC 中的描述：
越來越多的 Web 協定需要在進行請求之前發現有關主機（「整站元數據」）的政策或其他信息。例如，Robots Exclusion Protocol （http://www.robotstxt.org）指定了一種方式供自動化處理過程獲取訪問資源的權限；同樣地，隱私偏好平台告訴用戶代理如何事先發現隱私政策。
儘管可以通過幾種方式訪問每個資源的元數據（例如 HTTP 標頭、WebDAV 的 PROPFIND[RFC4918]），但與它們相關的客戶端感知延遲和/或部署困難的開銷通常限制了在這些情況下它們的使用。
當這種情況發生時，通常會指定一個「知名位置」來存儲這樣的資料，以便輕鬆定位。但是，這種方法的缺點是會冒著與其他「知名位置」和現有資源產生衝突的風險。
為應對這一問題，本備忘錄為這些「知名位置」的 HTTP（S）URI 定義了一個路徑前綴，“/.well-known/”。未來的規範可以註冊它們的使用，以避免碰撞並最大限度地減少對網站 URI 空間的侵擾。
為了使用此插件的設置頁面，您需要具有「manage_options」權限。
外掛標籤
開發者團隊
原文外掛簡介
This plugin enables “Well-Known URIs” support for WordPress (RFC 5785: http://tools.ietf.org/html/rfc5785).
From the RFC:
It is increasingly common for Web-based protocols to require the
discovery of policy or other information about a host (“site-wide
metadata”) before making a request. For example, the Robots
Exclusion Protocol http://www.robotstxt.org/ specifies a way for
automated processes to obtain permission to access resources;
likewise, the Platform for Privacy Preferences
tells user-agents how to discover privacy policy beforehand.
While there are several ways to access per-resource metadata (e.g.,
HTTP headers, WebDAV’s PROPFIND [RFC4918]), the perceived overhead
(either in terms of client-perceived latency and/or deployment
difficulties) associated with them often precludes their use in these
scenarios.
When this happens, it is common to designate a “well-known location”
for such data, so that it can be easily located. However, this
approach has the drawback of risking collisions, both with other such
designated “well-known locations” and with pre-existing resources.
To address this, this memo defines a path prefix in HTTP(S) URIs for
these “well-known locations”, “/.well-known/”. Future specifications
that need to define a resource for such site-wide metadata can
register their use to avoid collisions and minimise impingement upon
sites’ URI space.
You will need ‘manage_options’ capability in order to use the Settings
page for this plugin.
