On 22 November 2012 22:14, Owen Marinas omari...@woozworld.com wrote:
option httpchk POST /db/data/ext/feed/graphdb/userFeed
HTTP/1.1\r\nContent-Type: application/json\r\nContent-Length:
35\r\n{userId:8, offset:0, limit:1}\r\n
It might not be related to your original question, but I think
Thx for the advice Jonathan
Willy's advice from an old post was to make it work with printf+nc in
bash first. So I did.
the issue is after I added the lines to the backend(below), the server
still resported UP eben if the expected string is not there.
regards
Owen
---
On 23 November 2012 17:10, Owen Marinas omari...@woozworld.com wrote:
Thx for the advice Jonathan
Willy's advice from an old post was to make it work with printf+nc in bash
first. So I did.
I think your back-end may be being lenient, then :-)
the issue is after I added the lines to the
I hate myself for this
my production LB is running haproxy-1.4.15-1 but the Staging haproxy-1.4.8-1
after upgrade its all working now, the POST, and http-check expect
works fine.
thx all
Owen
On 12-11-23 12:50 PM, Jonathan Matthews wrote:
On 23 November 2012 17:10, Owen Marinas
On Fri, Nov 23, 2012 at 01:28:38PM -0500, Owen Marinas wrote:
I hate myself for this
my production LB is running haproxy-1.4.15-1 but the Staging haproxy-1.4.8-1
after upgrade its all working now, the POST, and http-check expect
works fine.
Good reason indeed. BTW, keep in mind that even
5 matches
Mail list logo