Lighttpd

Thank you for the last of help. When it comes time to ascend to another dimension I can use the terse language, condencending attitude, and references to RegEx, none of which I have found in your documentation. I have read alot of the other posts here, and you know, I know what I do not know, and I know what I know, and I know when to ask for help.

I hope someday that when you need help on software you decided to try that other people are nicer in that user group, lighttpd is only one piece of the world to get control away from these Microsofts of the world. I just don't understand the mean attitude and snippy comments everytime someone puts an issue here.

And I am sorry for using high, cause it was high to me, I thought that is what it mean, I do not know your priorities. And I did not know any any limitations, how would I.

I hope you enjoy your web server, because people don't need snippy rude people in the life, nor do I need to use your projects software.

orb wrote:

Hi there, i am using lighty for a image server.

The host is Centos 4.4, under

I have 38 domains using that instance of lighty on say port 100.

Blow is my snippit with nested loops. Basically it craps out around domain 28, and causes a parse error, and I have tried many combos and it is when it exceeds that number, it causes an error.

$HTTP["referer"] !~ "^http://www.domain1.com" {
$HTTP["referer"] !~ "^http://www.domain2.com" {
$HTTP["referer"] !~ "^http://www.domain3.com" {
url.access-deny = ( ".jpg", ".jpeg", ".png", ".gif" )
}
}
}

I am looking for a work around. Can I put more than one domain inside the referrer test to maybe see if they will work, or tweak something else. And if there is no other solutions, is the best way to run another instance of lighty.

Also, considering this instance is just used as a image server, is there any special configs you can suggest, and anything I can strip out of my config.

Thanks.

My reply was not ment to be rude (I don't think it is). I told you what your problem is and how to fix it / do it correctly.
I explained that setting priority to high is for severe bugs.

And please don't make a big discussion out of this here in the bugtracker. If you feel like discussing, feel free to use the forum.
Again, this is not ment to be rude.