> If you set LogLevel to debug, midgard will log the reason why access
> is denied. Should be interesting because there are only a few
> situations where I know midgard can deny access without hitting the
> database: when the database connection wasn't set up, when no username
> was supplied, or when the username was too long (80 characters).
Username was 'admin' ... error_log shows:
[Fri May 11 10:36:22 2001] [debug] mod_midgard.c(1195): [client
62.96.245.19] midgard_translate_handler(latin1,
http://cms.fitzandfriends.de:80/nadmin/newframeset/)
[Fri May 11 10:36:22 2001] [debug]
/usr/local/midgard-1.4.1/include/midgard/select_db.h(24): [client
62.96.245.19] Midgard: select_database opened ffn_preview
[Fri May 11 10:36:22 2001] [debug]
/usr/local/midgard-1.4.1/include/midgard/select_db.h(8): [client
62.96.245.19] Midgard: select_database kept current (ffn_preview)
[Fri May 11 10:36:22 2001] [debug] mod_midgard.c(1292): [client
62.96.245.19] Midgard: using style #6 (7 elements)
[Fri May 11 10:36:22 2001] [debug]
/usr/local/midgard-1.4.1/include/midgard/select_db.h(8): [client
62.96.245.19] Midgard: select_database kept current (ffn_preview)
;-((, Kai
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
