From f5e7c4b8dcec15802d21a1b013bccd8536cc30e5 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Tue, 7 Apr 2026 13:03:37 +0200 Subject: [6.0.x] Updated Apache links to the current docs. Backport of 74e73dc1315d696330621a7f08310a2e87ea0eba from main --- docs/howto/deployment/wsgi/apache-auth.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/howto/deployment/wsgi/apache-auth.txt b/docs/howto/deployment/wsgi/apache-auth.txt index 454abf232c..2a81f78946 100644 --- a/docs/howto/deployment/wsgi/apache-auth.txt +++ b/docs/howto/deployment/wsgi/apache-auth.txt @@ -5,7 +5,7 @@ How to authenticate against Django's user database from Apache Since keeping multiple authentication databases in sync is a common problem when dealing with Apache, you can configure Apache to authenticate against Django's :doc:`authentication system ` directly. This -requires Apache version >= 2.2 and mod_wsgi >= 2.0. For example, you could: +requires Apache version >= 2.2 and ``mod_wsgi`` >= 2.0. For example, you could: * Serve static/media files directly from Apache only to authenticated users. @@ -23,7 +23,7 @@ requires Apache version >= 2.2 and mod_wsgi >= 2.0. For example, you could: auth handler if your custom cannot conform to these requirements. .. _Subversion: https://subversion.apache.org/ -.. _mod_dav: https://httpd.apache.org/docs/2.2/mod/mod_dav.html +.. _mod_dav: https://httpd.apache.org/docs/current/mod/mod_dav.html Authentication with ``mod_wsgi`` ================================ @@ -66,7 +66,7 @@ password that it receives from the prompt. In this example, the application :doc:`that is created by django-admin startproject `. -.. admonition:: Using Apache 2.2 with authentication +.. admonition:: Using Apache 2.2+ with authentication Make sure that ``mod_auth_basic`` and ``mod_authz_user`` are loaded. -- cgit v1.3