Jono Alderson

Manage your website’s <code>.well-known</code> files with ease using this powerful yet simple plugin. The Well-Known File Manager provides a user-friendly interface to create, edit and manage standardized <code>.well-known</code> files – essential components for modern web security, app associations, and service discovery.
Whether you need to implement security.txt for vulnerability reporting, configure app associations, or set up protocol handlers, this plugin handles the technical complexities while giving you complete control. It creates actual files on your server for maximum compatibility and performance, without requiring any special server configuration or technical knowledge.
Perfect for developers, site owners, and administrators who want a reliable way to manage their site’s <code>.well-known</code> directory through a clean, intuitive WordPress interface.
Key Features:
<ul>
<li>Easy Management: Simple toggle switches to enable/disable <code>.well-known</code> files</li>
<li>Physical File Creation: Creates actual files in the <code>.well-known</code> directory for maximum compatibility</li>
<li>Content Editing: Built-in content editor for each file type with syntax highlighting</li>
<li>Default Templates: Pre-configured templates for common <code>.well-known</code> files</li>
<li>Validation: Content validation to ensure files meet required standards</li>
<li>Priority Files: Highlighted support for important files like <code>security.txt</code>, <code>assetlinks.json</code>, and <code>apple-app-site-association</code></li>
<li>Automatic Cleanup: Removes files when disabled to keep your server clean</li>
<li>Data Preservation: Files and settings are preserved when the plugin is deactivated or uninstalled</li>
</ul>
Supported Files:
<ul>
<li>Security Files: <code>security.txt</code>, <code>security-txt</code></li>
<li>App Associations: <code>assetlinks.json</code>, <code>apple-app-site-association</code></li>
<li>Protocol Handlers: <code>change-password</code>, <code>gpc</code>, <code>hoba</code></li>
<li>Discovery: <code>host-meta</code>, <code>host-meta.json</code>, <code>nodeinfo</code></li>
<li>Authentication: <code>openid-configuration</code>, <code>oauth-authorization-server</code></li>
<li>And many more…</li>
</ul>
How It Works:
This plugin takes a physical file approach rather than routing requests through WordPress:
<ul>
<li>When Enabled: Creates actual files in your <code>.well-known</code> directory</li>
<li>When Disabled: Removes the files from your server</li>
<li>No Server Configuration: Works on any hosting setup without requiring <code>.htaccess</code> modifications</li>
<li>Maximum Compatibility: Files are served directly by your web server for optimal performance</li>
</ul>
Benefits:
<ul>
<li>Universal Compatibility: Works on any hosting provider without special configuration</li>
<li>Better Performance: Files are served directly by the web server, not through WordPress</li>
<li>Simplified Setup: No need to configure rewrite rules or server settings</li>
<li>Automatic Management: Files are created and removed automatically based on your settings</li>
<li>Clean Server: Disabled files are completely removed from your server</li>
<li>Data Safety: Your files and settings remain intact when deactivating or uninstalling the plugin</li>
</ul>

Well-Known File Manager

Manage files in the .well-known directory with ease.

Matthias Pfefferle

mrose17

This plugin enables “Well-Known URIs” support for WordPress (RFC 5785: http://tools.ietf.org/html/rfc5785).
From the RFC:
<blockquote>
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 <a href="http://www.robotstxt.org/" rel="nofollow ugc">http://www.robotstxt.org/</a> 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.
</blockquote>
You will need ‘manage_options’ capability in order to use the Settings 
page for this plugin.

Well-Known File Manager vs /well-known-uris/