Project

General

Profile

Actions

Bug #1117

closed

mod_auth not working

Added by admin almost 18 years ago. Updated over 16 years ago.

Status:
Invalid
Priority:
Normal
Category:
mod_auth
Target version:
-
ASK QUESTIONS IN Forums:

Description

Hi,

I'm using this as 10-ssl.conf, but the auth.require appears to be
ineffective (it's served without authentication request).
I don't get errors during startup.
Does anyone know what's wrong with this?

$SERVERsocket == "0.0.0.0:443" {
ssl.engine = "enable"
ssl.pemfile = "/etc/lighttpd/server.pem"

status.status-url = "/server-status" 
status.config-url = "/server-config"
auth.backend = "htdigest" 
auth.backend.htdigest.userfile = "/etc/lighttpd/digest"
auth.require = (
"/server-config" =>
(
"method" => "digest",
"realm" => "Protected",
"require" => "valid-user"
),
"/server-status" =>
(
"method" => "digest",
"realm" => "Protected",
"require" => "valid-user"
)
)
}
Actions #1

Updated by darix almost 18 years ago

could it be mod_auth is loaded after mod_status?

Actions #2

Updated by admin almost 18 years ago

That's the case, yes.
I'd say it's still a bug though.

Actions #3

Updated by darix almost 18 years ago

does it help when you change the module load order?

Actions #4

Updated by admin almost 18 years ago

Yes, that works around this bug. :)

Actions #5

Updated by admin almost 18 years ago

I'm just wondering, why does this not apply to fastcgi?

Actions #6

Updated by stbuehler over 16 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

fastcgi returns HANDLER_GO_ON, as it needs more time to generate the response; mod_status however immediatly generates the content and returns HANDLER_FINISHED.

That the module order is something important is no bug imho (its by design), and the example loads auth before status.

Actions #7

Updated by stbuehler over 16 years ago

  • Status changed from Fixed to Invalid
Actions

Also available in: Atom