Monitor Authenticating proxy

Thanks Steve for the reply, I have tried curl as below,

curl http://www.google.com --proxy 89.2.43.110:80 -U r7b:test --proxy-ntlm -v

And found below reply, About to connect() to proxy 89.2.43.110 port 80 (0) * Trying 89.2.43.110... connected * Connected to 89.2.43.110 (89.2.43.110) port 80 (0) * Proxy auth using NTLM with user 'r7b'

GET http://www.google.com HTTP/1.1

Proxy-Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=

User-Agent: curl/7.19.7 (i686-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3 libidn/0.6.5

Host: www.google.com

Accept: /

Proxy-Connection: Keep-Alive

< HTTP/1.1 407 Proxy Authentication Required

< Proxy-Authenticate: NTLM TlRMTVNTUAACAAAACQAJADgAAAAGgokAkREv22yFgKEAAAAAAAAAAIQAhABBAAAABQCTCAAAAA9NR1JPVVBORVQCABIATQBHAFIATwBVAFAATgBFAFQAAQAUAEYARABZAEkATgBFAFQAQgBDADEABAAaAE0ARwBSAE8AVQBQAE4ARQBUAC4AQwBPAE0AAwAwAGYAZAB5AGkAbgBlAHQAYgBjADEALgBtAGcAcgBvAHUAcABuAGUAdAAuAGMAbwBtAAAAAAA=

< Cache-Control: no-cache

< Pragma: no-cache

< Content-Type: text/html; charset=utf-8

< Proxy-Connection: Keep-Alive

< Set-Cookie: BCSI-CS-7d06572a9586553b=2; Path=/

< Connection: Keep-Alive

< Content-Length: 3519

<

• Ignoring the response-body
• Connection 0 to host 89.2.43.110 left intact
• Issue another request to this URL: 'http://www.google.com'
• Re-using existing connection! (0) with host 89.2.43.110
• Connected to 89.2.43.110 (89.2.43.110) port 80 (0)
• Proxy auth using NTLM with user 'r7b'

GET http://www.google.com HTTP/1.1

Proxy-Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAAAwADAHAAAAAHAAcAcwAAAAAAAAAAAAAABoKJALAR3vHczABkAAAAAAAAAAAAAAAAAAAAAN/jh1Ml/PxUuQAlpK1a3QDWqts1zSHtiHI3YkZEWUxCMTA=

User-Agent: curl/7.19.7 (i686-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8y zlib/1.2.3 libidn/0.6.5

Host: www.google.com

Accept: /

Proxy-Connection: Keep-Alive

< HTTP/1.1 200 OK

< Date: Thu, 05 Dec 2013 11:27:00 GMT

< Expires: -1

< Cache-Control: private, max-age=0

< Content-Type: text/html; charset=ISO-8859-1

< P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657 for more info."

< Server: gws

< X-XSS-Protection: 1; mode=block

< X-Frame-Options: SAMEORIGIN

< Alternate-Protocol: 80:quic

< Transfer-Encoding: chunked

< Proxy-Connection: Keep-Alive

< Connection: Keep-Alive

< Set-Cookie: PREF=ID=1442564a06c7befc:FF=0:TM=1386242820:LM=1386242820:S=uEG4ulBH4lbFPP8I; expires=Sat, 05-Dec-2015 11:27:00 GMT; path=/; domain=.google.com

< Set-Cookie: NID=67=mRO5WVD-coHnV6hm7SyyetuTapMZ04xB0_C1lTMT5yRlgKMI1nj_JohiIbFGm_c_eRskjfxeIccejtMzBm99QsxbrZw76pPMHRhnS5qJA859esiqFeHlQ88QBVvd0q_s; expires=Fri, 06-Jun-2014 11:27:00 GMT; path=/; domain=.google.com; HttpOnly

Based on the curl output I have modified monitor with Proxy authorization parameter below is get string,

"GET HTTP://www.google.com/ HTTP/1.1\r\nProxy-Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA= \r\nHost: www.google.com\r\nAccept: /\r\nProxy-Connection: Close\r\nConnection: Close\r\n\r\n"

but still Pool members are showing down.