All releases of Siege

Release Notes: With this release, siege changes the way it handles --reps=once. It now divides a urls.txt file evenly among all its users, and each URL in the file is hit exactly once. This release also includes several fixes and a documentation update.

Release Notes: This release fundamentally alters one aspect of the program's behavior. In the past, when you ran it with --reps=once, each simulated user would hit each URL in the file exactly once. Now when you invoke --reps=once, siege divides the file among all its users and each URL in the file is hit exactly once. This release also adds support for HTTP-303 and includes several minor fixes.

Release Notes: This release addresses another inconsistency between the HTTP standard and practice. While RFC 2616 allows a port designation in the Host header, it confuses too many implementations for Siege to continue to send it. This version also fixes several significant bugs. All Siege users should update to this version.

Release Notes: This release fixes several bugs related to HTTP POST. Extra white space that could work its way into the request from user inputs has been eliminated. A memory leak in POST requests has been closed. -T/--content-type now works as expected.

Release Notes: Although RFC 2616 section 14.23 clearly states that a host header may contain an optional port, many servers ignore the option, and some of those requests may fail. This release removes ":port" from the host header in order to reduce "failures" by playing to the least common denominator.

Release Notes: RFC 2616 specifies that Location directives must contain an absolute URL, but most browsers normalize a relative one. With this release, siege now follows the browser convention. This version also includes a new default user-agent that complies with RFC 2616. That should silence the types of Web servers that like to complain about that sort of thing.

Release Notes: Although RFC 2616 specifies that Location directives must contain an absolute URI, most Web clients normalize relative URIs. This release adds conventional compliance with relative URI handling. Ironically, it also includes a new default user-agent so that field is in compliance with RFC 2616.

Release Notes: This release features one prominent new feature, URL escaping. Reserved characters are %-encoded as per RFC 3986. This release also features numerous bugfixes such as improved variable evaluation in the urls.txt file, dynamic Accept-Encoding, improved siegerc parsing, and several memory fixes.