Hi Daniel,

I do have some particulars that I should have included:

-----Original Message-----
From: Daniel Stenberg [mailto:daniel_at_haxx.se]
Sent: Wednesday, April 09, 2003 2:22 AM
To: libcurl Mailing list
Subject: Re: CURLE_COULDNT_RESOLVE_PROXY and BigIP and clustering

On Tue, 8 Apr 2003, Themmen, Joel wrote:

> I have received (finally) some information from our installation site.
> Apparently, they are using a product called BigIP (which they use for load
> balancing). So - now my question changes a little bit. Does anyone have
any
> experience with load balancing and libcurl.

I think the question is a bit too generic. "load balancing" can be done
multiple ways, especially when involving HTTP.

JCT: Right - understood. I should have clarified and asked load balancing
with BigIP and libcurl.

> I have no idea and would not even know where to start but if someone can
> point me in the right direction it would be greatly appreciated. In fact,
I
> do not even know that libcurl can work with BigIP (I think so but do not
> know enough to even really assert that).

I can't tell for sure either, but I would be surprised if they made one that
doesn't work with normal TCP/IP clients doing things right. The question is
of course if libcurl is doing all things right... :-)

Can you lookup the names properly manually with nslookup/dig and connect
with
telnet ?

JCT: We will try this first thing tomorrow morning but we have done is:

JCT: One of my guys compiled this documentation for the client:

***************************************************************
***************************************************************

Here's a rundown of an experiment I did:

I went into unix and typed:

  telnet bus-is1-vnd4a.ntrs.com 3525

This connected and told me that the ip I had connected to was
192.168.150.61.

So I typed:

  telnet 192.168.150.61 3525

and it also connected.

I went into Internet explorer and typed:

  http://bus-is1-vnd4a.ntrs.com:3525/npo.tnt/contactlist

which gave me a "bad request" error which is what we'd expect.

I tried:

  http://192.168.150.61:3525/npo.tnt/contactlist

and it returned the same. So far so good.

Now I went into unix and typed:

  lynx http://bus-is1-vnd4a.ntrs.com:3525/npo.tnt/contactlist

this returned a "bad request" error which is good.

Then I tried:

  lynx http://192.168.150.61:3525/npo.tnt/contactlist

And got a "Alert: Could not connect" error. This is bad.

***************************************************************
***************************************************************

So - Telnet seems OK.

And - it seems that if we use the URL or the raw IP we are OK in IE.

And - it seems that if we use the URL we are OK but the raw IP causes issues
when using lynx (although I am unsure of really why this happened).

I could offer some rationale here but honestly, I will only proceed to make
myself look stupid. You know far more then me and you are far better suited
to draw conclusions. I will, obviously, conduct any experimentation you want
me to try.

> PS - The BigIP website is http://www.f5.com/f5products/bigip/

I looked for a "questions and answers" section with perhaps more in-depth
details, but I couldn't fine any.

JCT: Interestingly, I read a review of BigIP and that review spoke highly of
the product but was critical of price and documentation.

Once again, thanks for the assistance.

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf