https://httpd.apache.org/docs/current/configuring.html
https://httpd.apache.org/docs/current/mod/directive-dict.html#Context
You would need to manually add .htaccess code from your root .htaccess file into your Apache Server’s httpd.conf file. The httpd.conf file allows you to create containers (<VirtualHost>, <Directory>, <Location>, <Files>, <If>, and <Proxy> containers) for where you want directives (rules) applied to. htaccess files instead are directory based and cannot use containers – wherever the .htaccess file is located then that is the directory/folder where directives (rules) will be applied and .htaccess files are hierarchical/recursive – if an .htaccess file does not exist in a child folder then the rules from the parent folder’s .htaccess file will be applied to child folders (subfolders).
You can add all the BPS Query String Exploits .htaccess code in the httpd.conf container where you choose to add them. For other BPS .htaccess code you should reference/cross reference the apache.org site to see which BPS .htaccess code is allowed, not useful or should not go in an httpd.conf file.
httpd allows for decentralized management of configuration via special files placed inside the web tree. The special files are usually called .htaccess, but any name can be specified in the AccessFileName directive. Directives placed in .htaccess files apply to the directory where you place the file, and all sub-directories. The .htaccess files follow the same syntax as the main configuration files. Since .htaccess files are read on every request, changes made in these files take immediate effect.
To find which directives can be placed in .htaccess files, check the Context of the directive. The server administrator further controls what directives may be placed in .htaccess files by configuring the AllowOverride directive in the main configuration files.
For more information on .htaccess files, see the .htaccess tutorial.
