• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Apache2.0 vs. Apache1.3 mod_auth

T

trauma

Guest
I'm currently running Plesk 7.5.4 on two different server platforms: RHEL2 and RHEL4.

RHEL2 uses Apache 1.3 and RHEL4 uses Apache 2.0. The issue that I'm noticing is related to how Apache handles authentication. I'm using both mod_auth and mod_auth_mysql. And I have a situation where I'm using mod_auth for the document root (it's actually frontpage that does this) and mod_auth_mysql for a subdirectory. This has worked fine in Apache1.3, but it's no bueno in Apache2.0.

In Apache2.0 it seems to always revert to the authentication mechanism imposed on the document root. It never even consults the database when trying to access the subdirectory. Shouldn't the settings for the subdirectory override those of the parent directory? It always has in the past.

btw all of this is handled with .htaccess files... if that makes any difference.
 
Back
Top