block access to drupal login with htaccess

Backdrop now includes support for the Security.txt standard via the security.txt module.htaccess file and restrict their access to your website. One could argue that the file should not be included on production in the first place, which is fair enough, but the same argument could be made for composer.lock. For example: package.json, composer.json and composer.lock.

If this issue is resolved and the two mentioned modules are approved then we could have something like: Limit logins and admin by IP order deny,allow. htaccess file, multiple files with potential sensitive information are blocked.

This may not be easy or indeed possible depending on a user's technical expertise or hosting arrangements.ĭraft of feature description for Press Release (1 paragraph at most)

well-known directory in their document root. Any module which wishes to serve a well-known URI should add a line to the 'Status Report' informing the user that they must manually create a.I will submit a PR with my proposed change shortly. htaccess file prevents these modules from working without the user manually patching their. There are a number of standardized well-known URIs which it would be good to allow Backdrop to serve, indeed I have started work on a general module to do this. without an exemption for those beginning with. htaccess file (as of version 1.21.4) blocks all files (and therefore Backdrop paths) beginning with. htaccess files do not deny access to files (and therefore Drupal paths) beginning with. This module serves a two well-known URLs: I have recently started to use Backdrop, and as my first development task I ported my Security.txt module from Drupal to Backdrop.

Block access to drupal login with htaccess