in reply to Load Balancing
in thread using Net::Telnet to test Apache

No matter what you use, be it Net::Telnet or IO::Socket or the LWP modules, if you connect to 'example.com' and that hostname is load balanced, you're going to get different servers handling the request, sure. Sorry, I didn't realize that was going to be an issue (it's the first time you brought it up). If you can access each server individually by IP, perhaps you can simply pass that URL to the LWP modules: e.g. http://192.0.0.1/page.html. If you're using virtual hosting such that the Host: header makes a difference, I guess you're better off using IO::Socket and speaking HTTP yourself. If there isn't a way you can reach an arbitrary server directly, I don't see how any of the methods presented can help you, as they'd all be influenced by the load-balancing setup.

Replies are listed 'Best First'.
RE: RE: Load Balancing
by meonkeys (Chaplain) on Nov 14, 2000 at 07:55 UTC
    Thank you. You have much knowledge in this area and your help is truly appreciated. I will give IO::Socket a go, and, of course, read more and more and more....
[reply]
      No, you're being lead down a dark tunnel with no cheese at the end again.

      There's nothing that using your IO::Socket code buys you as far as distinguishing a "load-balanced web server", whatever you mean by that.

      If you have 10 "A" records for "www.someserver.com", then look those up and use the specific IP in your URL, and then be sure to add a "host" header to get the right virtual server, if that makes a difference in your testing.

      Please stop refuting the advice of people whom you are asking advice of, unless you've got some good rebuttal. Sheesh.

      -- Randal L. Schwartz, Perl hacker

[reply]

In Section Seekers of Perl Wisdom