An Apache project has an existing website which includes hundreds or even thousands of static .html pages of documentation and other materials. The project wants to be able to publish the website using Apache infrastructure without having to check many megabytes of content that is now in Subversion into Git.
The first plan was to use AliasMatch to map the current locations of the static .html pages, and use those aliases with Apache's .htaccess configuration file to work with Apache Web Service software. Unfortunately, AliasMatch is not allowed in .htaccess.
The second, successful plan, is to use "mod-rewrite".
The fix consists of two parts:
One downside is that, in theory, anyone could reach every Apache website by hand-crafting a URL like:
Apache HTTPD does not have this concept of defining the URI path as "internal" to prevent such access.
The details of the situation the Lucene project faced, and how the project and Infra crafted a solution, are in the comments on INFRA-19439: "Add a way to publish static HTML content of huge size (outside of pelican CMS) without checking it into Git."
There is no content with the specified labels