Remove documentation related to older Apache versions.

Author: GrahamDumpleton

docs/configuration-directives/WSGIAcceptMutex.rst

@@ -16,6 +16,6 @@ will be used. If set the method types are the same as for the Apache
 `AcceptMutex`_ directive.
 
 Note that the ``WSGIAcceptMutex`` directive and corresponding features are
-not available on Windows or when running Apache 1.3.
+not available on Windows.
 
 .. _AcceptMutex: http://httpd.apache.org/docs/2.4/mod/mpm_common.html#acceptmutex

docs/configuration-directives/WSGIAuthUserScript.rst

@@ -15,9 +15,9 @@ about the handshaking related to HTTP Basic and Digest authentication and
 you only wish to deal with supplying the user credentials for authenticating
 the user.
 
-If using at least Apache 2.2, other Apache modules implementing custom
-authentication mechanisms can also make use of the authentication provider
-if they are using the corresponding Apache C API for accessing them.
+Other Apache modules implementing custom authentication mechanisms can also
+make use of the authentication provider if they are using the corresponding
+Apache C API for accessing them.
 
 More detailed information on using the WSGIAuthUserScript directive can be
 found in :doc:`../user-guides/access-control-mechanisms`.

docs/configuration-directives/WSGIProcessGroup.rst

@@ -59,7 +59,7 @@ different virtual host. Which daemon process groups can be selected may be
 further restricted if the WSGIRestrictProcess directive has been used.
 
 Note that the WSGIProcessGroup directive and corresponding features are not
-available on Windows or when running Apache 1.3.
+available on Windows.
 
-.. _SetEnv: http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv
-.. _RewriteRule: http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriterule
+.. _SetEnv: http://httpd.apache.org/docs/2.4/mod/mod_env.html#setenv
+.. _RewriteRule: http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewriterule

docs/configuration-directives/WSGIRestrictProcess.rst

@@ -59,6 +59,6 @@ WSGI applications to different daemon process groups using the
   </Files>
 
 Note that the WSGIDaemonProcess directive and corresponding features are
-not available on Windows or when running Apache 1.3.
+not available on Windows.
 
-.. _SetEnv: http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv
+.. _SetEnv: http://httpd.apache.org/docs/2.4/mod/mod_env.html#setenv

docs/configuration-directives/WSGISocketPrefix.rst

@@ -40,4 +40,4 @@ one that is only writable by 'root' user, or if not starting Apache as
 'root', the user that Apache is started as.
 
 Note that the WSGISocketPrefix directive and corresponding features are not
-available on Windows or when running Apache 1.3.
+available on Windows.

docs/requirements.rst

@@ -2,23 +2,15 @@
 Requirements
 ============
 
-The mod_wsgi package can be compiled for and used with most recent patch
-revisions of Apache 2.0, 2.2 or 2.4 on UNIX like systems, such as Linux and
-MacOS X, as well as Windows.
-
-It is highly recommended that you use Apache 2.4. Older versions of Apache
-have architectural design problems and sub optimal configuration defaults,
-that can result in excessive memory usage in certain circumstances. More
-recent mod_wsgi versions attempt to protect against these problems in
-Apache 2.0 and 2.2, however it is still better to use Apache 2.4.
+The mod_wsgi package can be compiled for and used with Apache 2.4 on UNIX
+like systems, such as Linux and MacOS X, as well as Windows.
 
 Any of the single threaded 'prefork' or multithreaded 'worker' and 'event'
 Apache MPMs can be used when running on UNIX like systems.
 
-Both Python 2 and 3 are supported. The minimum recommended versions of each
-being Python 2.6 and 3.3 respectively. The Python installation must have
-been installed in a way that shared libraries for Python are provided such
-that embedding of Python in another application is possible.
+Python 3.10 or later is required. The Python installation must have been
+installed in a way that shared libraries for Python are provided such that
+embedding of Python in another application is possible.
 
 The mod_wsgi package should be able to host any Python web application
 which complies with the WSGI_ specification (PEP 3333). The

docs/user-guides/access-control-mechanisms.rst

@@ -41,11 +41,11 @@ shaking with the client to indicate whether the client is permitted access.
 Apache Authentication Provider
 ------------------------------
 
-When Apache 2.2 was released, it introduced the concept of authentication
-providers. That is, Apache implements the hand shaking with the client for
-authentication mechanisms such as Basic and Digest. All that the user
-server side code needs to provide is a means of authenticating the actual
-credentials of the user trying to gain access to the site.
+Apache implements the concept of authentication providers. That is, Apache
+implements the hand shaking with the client for authentication mechanisms
+such as Basic and Digest. All that the user server side code needs to
+provide is a means of authenticating the actual credentials of the user
+trying to gain access to the site.
 
 This greatly simplified the implementation of client authentication as the
 hand shaking for a particular authentication mechanism was implemented only
@@ -58,7 +58,7 @@ directive to define a Python script file containing code which performs the
 authenticating of user credentials as outlined.
 
 The required Apache configuration for defining the authentication provider
-for Basic authentication when using Apache 2.2 would be::
+for Basic authentication would be::
 
     AuthType Basic
     AuthName "Top Secret"
@@ -81,8 +81,8 @@ that the password is correct. If the user does not exist at all, then the
 result should be 'None'. If the user does exist, the result should be
 'True' or 'False' depending on whether the password was valid.
 
-If wishing to use Digest authentication, the configuration for Apache 2.2
-would instead be::
+If wishing to use Digest authentication, the configuration would instead
+be::
 
     AuthType Digest
     AuthName "Top Secret"
@@ -136,13 +136,7 @@ provider can also be defined::
     WSGIScriptAlias / /usr/local/django/mysite/apache/django.wsgi
 
     <Directory /usr/local/django/mysite/apache>
-    <IfVersion < 2.4>
-	Order allow,deny
-	Allow from all
-    </IfVersion>
-    <IfVersion >= 2.4>
-	Require all granted
-    </IfVersion>
+    Require all granted
 
     WSGIApplicationGroup django
 
@@ -189,21 +183,6 @@ Any configuration defined by !SetEnv directives is not passed in the
 configuration specified in such a way from a '.htaccess' file.
 Configuration should as a result be placed into the script file itself.
 
-Although authentication providers were a new feature in Apache 2.2, the
-mod_wsgi module emulates the functionality so that the above can also be
-used with Apache 2.0. In using Apache 2.0, the required Apache configuration
-is however slightly different and needs to be::
-
-    AuthType Basic
-    AuthName "Top Secret"
-    WSGIAuthUserScript /usr/local/wsgi/scripts/auth.wsgi
-    AuthAuthoritative Off
-    Require valid-user
-
-When using Apache 2.0 however, only support for Basic authentication
-mechanism is provided. It is not possible to use Digest authentication.
-When using Apache 1.3, this feature is not available at all.
-
 The benefit of using the Apache authentication provider mechanism rather
 than the WSGI application doing it all itself, is that it can be used to
 control access to a number of WSGI applications at the same time as well as
@@ -252,9 +231,6 @@ Any configuration defined by !SetEnv directives is not passed in the
 configuration specified in such a way from a '.htaccess' file.
 Configuration should as a result be placed into the script file itself.
 
-Configuration of group authorisation is the same whether Apache 2.0 or 2.2
-is used. The feature is not available when using Apache 1.3.
-
 By default the group authorisation code is always executed in the context
 of the first interpreter created by Python, ie., '%{GLOBAL}', and always in
 the Apache child processes, never in a daemon process. The interpreter can

docs/user-guides/application-issues.rst

@@ -1119,8 +1119,7 @@ WSGIDaemonProcess directive::
 
     WSGIDaemonProcess example stack-size=524288
 
-If you are unable to upgrade to Apache 2.2 and/or mod_wsgi 2.0, the only
-other option you have for affecting the amount of virtual memory set aside
+Another option you have for affecting the amount of virtual memory set aside
 for the stack of each thread is to override the process stack size. If you are
 using a standard Apache distribution, this can be done by adding to the
 'envvars' file for the Apache installation::

docs/user-guides/checking-your-installation.rst

@@ -277,13 +277,9 @@ directives are used.
 
 If the AcceptMutex directive is defined in the Apache configuration file,
 then what ever mechanism is specified will be used instead for Apache child
-processes. Provided that Apache 2.2 or older is used, and WSGIAcceptMutex
-is not specified, then when AcceptMutex is used, that will also then be used
-by mod_wsgi daemon processes as well.
-
-In the case of Apache 2.4 and later, AcceptMutex will no longer override the
-default for mod_wsgi daemon process groups, and instead WSGIAcceptMutex must
-be specified seperately if it needs to be overridden for both.
+processes. AcceptMutex will not override the default for mod_wsgi daemon
+process groups, and instead WSGIAcceptMutex must be specified separately if
+it needs to be overridden for both.
 
 Either way, you should check the Apache configuration files as to whether
 either AcceptMutex or WSGIAcceptMutex directives are used as they will