Do not use HTTP Spew for connecting to servers outside of your LAN. Do not use HTTP Spew without the permission of your server admins. Use HTTP Spew if you wish you could kinda multicast with HTTP...
No support for bidirectional HTTP streaming
No support for "Expect: 100-continue" headers/responses
No support for DNS resolution (WONTFIX, ever)
No support for HTTPS
No support for keepalive (yet?)
Not remotely RFC-compliant
Messes up analytics/reporting on servers
Resets server connections
May get you banned from the Internet!
HTTP Spew lets you fire off identical (or similar) requests to multiple HTTP servers and wait for any number (or all) of them to complete or for a timeout to expire.
HTTP Spew may be useful for implementing reverse proxy servers if you 1) can't decide on a load balancing strategy for them 2) have much more hardware than you actually use
It's also completely untested and unused anywhere!
You can get the latest source via git from the following locations:
git://bogomips.org/http_spew.git git://repo.or.cz/http_spew.git (mirror)
You may browse the code from the web and download the latest snapshot tarballs here:
Inline patches (from "git format-patch") to the mailing list are preferred because they allow code review and comments in the reply to the patch.
We will adhere to mostly the same conventions for patch submissions as git itself. See the Documentation/SubmittingPatches document distributed with git on on patch submission guidelines to follow. Just don't email the git mailing list or maintainer with http_spew patches.
All feedback (bug reports, user/development discussion, patches, pull requests) go to the mailing list: firstname.lastname@example.org
Mailing list archives may be viewed and downloaded here:
mail archives: https://bogomips.org/http_spew-public/ public: email@example.com source code: git clone https://bogomips.org/http_spew.git git clone git://bogomips.org/http_spew.git