Requesting a built-in toggle or setting within the MyKinsta dashboard (under Tools or Security) that allows site owners to block public HTTP access to Markdown (.md) files.
Problem / Use Case:
Modern development workflows, themes, plugins, and frameworks frequently include .md files (such as README.md, CHANGELOG.md, or internal documentation) directly in public directories. Publicly exposing these files can lead to unwanted information disclosure—exposing plugin/theme versions, repository paths, or technical setup details to potential scanners and attackers.
Currently, restricting access to .md files on Kinsta requires opening a ticket with support to manually update the NGINX server block configuration.
Proposed Solution:
Add a native option in the MyKinsta dashboard—similar to existing tools like IP Deny or SSL management—that lets users:
-
Enable a global rule to deny direct access (return 403 Forbidden) for all
.mdfiles. -
Toggle this rule on or off per site/environment (Staging vs. Production) without needing to contact support