[DOCS] Add directive to deny access for current Apache

The example in the note shows how to deny access up to Apache 2.2.
The directive for the current version is added.

Resolves: #90433
Releases: master, 9.5
Change-Id: I7842af8acdf632aebab8b8f63637450efd4fa23c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63321


Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Björn Jacob <bjoern.jacob@tritum.de>
Tested-by: Ralf Zimmermann <ralf.zimmermann@tritum.de>
Reviewed-by: Björn Jacob <bjoern.jacob@tritum.de>
Reviewed-by: Ralf Zimmermann <ralf.zimmermann@tritum.de>

typo3/sysext/form/Documentation/I/Concepts/FormFileStorages/Index.rst

@@ -41,13 +41,22 @@ desired upload storage.
    In principle, files in filemounts are publicly accessible. If the
    uploaded files could contain sensitive data, you should suppress any
    HTTP access to the filemount. This may, for example, be achieved by
-   creating a .htaccess file, assuming you are using an Apache web server.
-   The directive of the .htaccess file is fairly easy:
-
-   .. code-block:: html
-
-      Order deny,allow
-      Deny from all
+   creating a :file:`.htaccess` file, assuming you are using an Apache web
+   server. The directive of the :file:`.htaccess` file is fairly easy:
+
+   .. code-block:: apache
+
+      # Apache ≥ 2.3
+      <IfModule mod_authz_core.c>
+         Require all denied
+      </IfModule>
+
+      # Apache < 2.3
+      <IfModule !mod_authz_core.c>
+         Order allow,deny
+         Deny from all
+         Satisfy All
+      </IfModule>
 
 The following code block shows you how to configure additional filemounts
 for form definitions.