[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fe5Cj9oEkyGU91V9HeDJaTq8tV_0p-MaN2PkziA9sNd8":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"mrose17","https:\u002F\u002Fprofiles.wordpress.org\u002Fmrose17\u002F",1,70,85,30,84,"2026-04-04T20:46:37.423Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":20,"num_ratings":20,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":28,"download_link":29,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":30,"fetched_at":31},"well-known-uris","\u002Fwell-known-uris\u002F","1.0.3","\u003Cp>This plugin enables “Well-Known URIs” support for WordPress (RFC 5785: http:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc5785).\u003C\u002Fp>\n\u003Cp>From the RFC:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>It is increasingly common for Web-based protocols to require the\u003Cbr \u002F>\n  discovery of policy or other information about a host (“site-wide\u003Cbr \u002F>\n  metadata”) before making a request.  For example, the Robots\u003Cbr \u002F>\n  Exclusion Protocol \u003Ca href=\"http:\u002F\u002Fwww.robotstxt.org\u002F\" rel=\"nofollow ugc\">http:\u002F\u002Fwww.robotstxt.org\u002F\u003C\u002Fa> specifies a way for\u003Cbr \u002F>\n  automated processes to obtain permission to access resources;\u003Cbr \u002F>\n  likewise, the Platform for Privacy Preferences\u003Cbr \u002F>\n  tells user-agents how to discover privacy policy beforehand.\u003C\u002Fp>\n\u003Cp>While there are several ways to access per-resource metadata (e.g.,\u003Cbr \u002F>\n  HTTP headers, WebDAV’s PROPFIND [RFC4918]), the perceived overhead\u003Cbr \u002F>\n  (either in terms of client-perceived latency and\u002For deployment\u003Cbr \u002F>\n  difficulties) associated with them often precludes their use in these\u003Cbr \u002F>\n  scenarios.\u003C\u002Fp>\n\u003Cp>When this happens, it is common to designate a “well-known location”\u003Cbr \u002F>\n  for such data, so that it can be easily located.  However, this\u003Cbr \u002F>\n  approach has the drawback of risking collisions, both with other such\u003Cbr \u002F>\n  designated “well-known locations” and with pre-existing resources.\u003C\u002Fp>\n\u003Cp>To address this, this memo defines a path prefix in HTTP(S) URIs for\u003Cbr \u002F>\n  these “well-known locations”, “\u002F.well-known\u002F”.  Future specifications\u003Cbr \u002F>\n  that need to define a resource for such site-wide metadata can\u003Cbr \u002F>\n  register their use to avoid collisions and minimise impingement upon\u003Cbr \u002F>\n  sites’ URI space.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>You will need ‘manage_options’ capability in order to use the Settings\u003Cbr \u002F>\npage for this plugin.\u003C\u002Fp>\n","\"Well-Known URIs\" for WordPress!",2672,0,"2016-11-03T13:20:00.000Z","4.6.30","3.5.1","",[26,27,14],"discovery","well-known","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwell-known-uris\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwell-known-uris.zip",null,"2026-03-15T15:16:48.613Z"]