內容簡介
此外掛可以讓 WordPress 支援「知名位置 (Well-Known URIs)」 (RFC 5785: http://tools.ietf.org/html/rfc5785)。
根據RFC：
越來越多的網路協定在發送請求前需要查詢有關主機（即整個站點的資料）的政策或其他資訊。例如，機器人排除協定（http://www.robotstxt.org/）規定了一種方法，使自動化程序可以獲得訪問資源的權限。同樣，隱私偏好平台可以告訴用戶代理在使用前如何查找隱私政策。
儘管有幾種方法可以訪問每個資源的元數據（例如HTTP標頭、WebDAV的PROPFIND [RFC4918]），但它們通常會引起相應的開銷（例如對客戶端的感知延遲和/或部署困難），因此不會在這些情況下使用。
當發生這種情況時，通常會指定一個「知名位置」以存放這些資料，以便可以輕鬆查找。但是，此方法的缺點是會存在与其他指定的「知名位置」和现有资源的碰撞風險。
為了解决此问题，本备忘录为这些「知名位置」定义了一个HTTP（S） URI中的路徑前缀，即「/.well-known/」。以後需要為此類站點整體元數據定義資源的未來版本可以註冊其使用，以避免碰撞和最小化對站點URI空间的侵害。
外掛標籤
開發者團隊
原文外掛簡介
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.
