Without knowing exactly what you mean by replay, here are two simple
options. Both assume you have a file called 'proxy.txt' that contains a
list of proxies and ports in the following format: <hostname|ip
address>:<port>. Both examples will loop through the list of proxies
sending the "same" request. Additional error handling should be added to
suit your needs.
$ cat proxy.txt
127.0.0.1:8080
10.0.0.100:8080
192.168.0.5:8080
Option #1 (using ncat) - this example assumes you have the complete HTTP
request (including protocol headers) in a file called 'http_request.txt'
and that you don't care about the result. If you want the result, send it
somewhere other than /dev/null. This example illustrates a simple GET
request.
$ cat http_request.txt
GET / HTTP/1.0
Host: www.example.com
$ for p in `cat proxy.txt`; do ncat --proxy ${p} www.example.com 80 <
http_request.txt > /dev/null; done
Option #2 (using curl) - using this method, the request will not be
exactly the same each time. Some of the HTTP headers will vary. This may
be desirable if you want to play with various protocol options when
sending a GET or POST. For simplicity sake, I will assume a GET request
in this example. The result in this example is also discarded.
$ for p in `cat proxy.txt`; do curl -s -x ${p} http://www.example.com >
/dev/null; done
--
byte_bucket
> Hi,
>
> I'm looking to do some research/testing and am looking to see if a tool
> exists which will replay an HTTP request over and over, and each time use
> a
> different proxy.
>
> Regards.
> _______________________________________________
> Pauldotcom mailing list
> [email protected]
> http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
> Main Web Site: http://pauldotcom.com
_______________________________________________
Pauldotcom mailing list
[email protected]
http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
Main Web Site: http://pauldotcom.com
