Hi Graeme,

I found that it was not because OK is an HTTP keyword that the check was 
not working,
but because OK is a substring of BR*OK*EN.

Daniel

Daniel Lemay wrote:
> Hi Graeme,
>
> You were correct. It is now working.
>
> Thank you
>
> Daniel
>
> Graeme Fowler wrote:
>> On Mon, 2009-05-25 at 16:19 +0000, Daniel Lemay wrote:
>>   
>>> T 192.168.58.56:7778 -> 192.168.58.2:60760 [AP]
>>>   HTTP/1.1 200 OK..Date: Mon, 25 May 2009 16:06:14 GMT..Server: 
>>>     
>>
>> Spot the OK above? ldirectord is matching on that.
>>
>> If you make your string something which isn't defined as a response code
>> in the HTTP protocol, you'll probably make it work :)
>>
>> Try:
>>
>> "SERVER_OK_RIGHT_NOW" for OK
>> "SERVER_BUSTED" for BROKEN
>>
>> Graeme
>>
>>
>> _______________________________________________
>> Please read the documentation before posting - it's available at:
>> http://www.linuxvirtualserver.org/
>>
>> LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
>> Send requests to lvs-users-requ...@linuxvirtualserver.org
>> or go to http://lists.graemef.net/mailman/listinfo/lvs-users
>>   
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
Send requests to lvs-users-requ...@linuxvirtualserver.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

Reply via email to