Project

General

Profile

Bug #1437

server.max-connections works in conditional?

Added by Anonymous almost 13 years ago. Updated almost 12 years ago.

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

Description

i am not sure, but according to the server status server.max-connections does not work in a conditional?

we use:

server.max-connections = <few>
$HTTPurl =~ "server-status" {
server.max-connections = <more than few>
}

and according to server status we always have <more than few> connections, even for non-status accesses.

-- w1zzard

#1

Updated by Anonymous almost 13 years ago

this is not supported.

#2

Updated by Anonymous almost 13 years ago

is there any mechanism that allows me to ensure access to server status even when the server is "full" ?

#3

Updated by stbuehler over 12 years ago

How could the server know if a client is allowed to connect if it has not the information the conditional needs?

Just use it only global, it does not work in a conditional.

And no, there is no mechanism to ensure access to the server status.

#4

Updated by Anonymous over 12 years ago

you could evaluate the server limit at a later stage and then turn the client away with a forbidden or temporarily unavailable? this is probably easier solved in a plugin. once 1.5 comes out i'll implement this

#5

Updated by stbuehler over 12 years ago

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

You could try mod_magnet and a lua script (http://trac.lighttpd.net/trac/wiki/Docs%3AModMagnet#user-tracking)

#6

Updated by stbuehler almost 12 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom