What's new in Siege 3.0.7
Oct 13, 2014
- This release fixes a bug introduced in siege-3.0.6. Rather than strictly adhere to the RFC, siege will construct an absolute URL from a relative one. While this is convenient it missed a usecase. Siege-3.0.6 barfs on Location: http://localhost All siege 3.0.6 users should upgrade to 3.0.7.
New in Siege 3.0.6 (Jan 9, 2014)
- Updated to include proxy directives
New in Siege 3.0.6 Beta 2 (Nov 1, 2013)
- Added support for HTTP-303.
New in Siege 3.0.5 (Oct 18, 2013)
- This version 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.
New in Siege 3.0.4 Beta 1 (Sep 13, 2013)
- 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.
New in Siege 3.0.3 (Aug 20, 2013)
- This version 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.
New in Siege 3.0.3 Beta 3 (Jul 31, 2013)
- This version fixes a siegerc parser bug which was inadvertently introduced in the 3.0.x line. In those versions, siege ignores entries with leading whitespace.
New in Siege 3.0.3 Beta 2 (Jul 26, 2013)
- This version adds URL escaping along with an option to turn the feature off.
- It also removes chunked encoding from -g/--get requests to make the output more human-readable.
New in Siege 3.0.2 (Jul 19, 2013)
- This release fixes a major bug in 3.0.1 that affected HTTP POST. All 3.0.1 users should upgrade to this version.
New in Siege 3.0.2 Beta 2 (Jul 13, 2013)
- This version features several minor bugfixes and enhancements.
New in Siege 3.0.2 Beta 1 (May 30, 2013)
- This version fixes an issue on Solaris which prevented siege from compiling on that platform.
New in Siege 3.0.1 (May 15, 2013)
- This version provides a new method for looping through a URLs file.
- Each client now begins at a different location in the file.
- It also provides support for long URLs and POST data and includes several bugfixes and documentation updates.
New in Siege 3.0.1 Beta 4 (May 9, 2013)
- This version updates the default siegerc file to provide a mechanism with which you can disable cookies.
New in Siege 3.0.1 Beta 3 (May 8, 2013)
- This version fixes a bug in which a host lookup failure could cause siege to erroneously send traffic to localhost.
New in Siege 3.0.1 Beta 1 (Apr 20, 2013)
- This version adds support for large headers and URLs.
- It also introduces a fundamentally different way to loop through a urls.txt file.
- Each simulated user starts from a different segment of the file so they don't all hit the same URLs at once.
New in Siege 3.0.0 Beta 3 (Mar 28, 2013)
- This version allows you to upload unique files to an FTP server.
- Siege will rename each one with a timestamp.
- The feature can be turned on/off with a .siegerc setting.
- It also features several code improvements.
New in Siege 3.0.0 Beta 2 (Mar 22, 2013)
- This version contains several bugfixes related to the FTP protocol.
New in Siege 3.0.0 Beta 1 (Mar 20, 2013)
- This version adds support for the FTP protocol and more complete support for RFC1738 URLs.
New in Siege 2.78 (Mar 12, 2013)
- This version fixes a header bug. When you assign an Accept: header with the -H/--header command line options, it will override the default Accept header.
New in Siege 2.77 (Mar 8, 2013)
- This version adds support for HTTP 307 redirects.
- It also includes several autotools corrections and some minor bugfixes.
New in Siege 2.75 (Mar 1, 2013)
- This version fixes a problem with HEAD requests using digest authentication.
New in Siege 2.74 (Feb 14, 2013)
- This release includes a minor fix to improve output format in verbose mode.
New in Siege 2.73 (Feb 12, 2013)
- This version includes numerous bugfixes and function ports so it will run better and compile on older systems.
- It also includes several new features such as timestamped output, a -q/--quiet option to suppress stdout, and conditional exits on -g/--get requests.
- On those requests, siege will now exit 0 if it receives at least one HTTP 200 response. Otherwise, it will exit 1.
- These last two features have been added to make the program more script-friendly.
New in Siege 2.73 Beta 8 (Feb 8, 2013)
- This version adds -q/--quiet to suppress most output. Quiet can be set at the commandline or inside a .siegerc file.
New in Siege 2.73 Beta 7 (Feb 7, 2013)
- On a --get request, siege will now exit 1 if the transaction doesn't contain at least one HTTP 200 response.
- This release also allows you to POST in a --get request.
New in Siege 2.72 (Sep 14, 2012)
- This release corrects a thirteen year old bug. If you don’t provide a ‘-f file’ argument, siege will now look for urls.txt inside the $sysconfdir you set at configure time.
New in Siege 2.73 Beta 5 (Sep 14, 2012)
- This version fixes a bug that prevented the display of HTML while in --debug/-D mode.
New in Siege 2.73 Beta 4 (Jul 31, 2012)
- This version addresses a bug in which siege wouldn't cancel cleanly on some platforms after ctrl-c.
New in Siege 2.73 Beta 3 (Jul 10, 2012)
- This version provides a commandline option to set the content-type, allows you to construct PUT, DELETE, and HEAD URLs, and allows you to set an HTTP method for -g/--get requests.
- If set to HEAD, it displays the header transaction
- If set to GET, it displays the page contents.
New in Siege 2.73 Beta 2 (Apr 18, 2012)
- This version refines the fix for Debian bug #665407 and adds conditionals for backward compatibility.
New in Siege 2.72 (Feb 17, 2012)
- This version corrects a thirteen year old bug. If you don't provide a '-f file' argument, siege will now look for urls.txt inside the $sysconfdir you set at configure time.
New in Siege 2.72 Beta 1 (Feb 11, 2012)
- This release fixes a 13-year bug.
- Siege now uses $sysconfdir/urls.txt as its default urls.txt file.
- This is in accordance with existing documentation.
New in Siege 2.71 Beta 7 (Jan 31, 2012)
- This version addresses warnings generated by aclocal-1.9.
- It also changes the default setting for verbose in siegerc from true to false.
New in Siege 2.71 Beta 3 (Dec 13, 2010)
- Fixed a syntax error which caused it to break
New in Siege 2.70 (Jul 17, 2010)
- This release provides a mechanism to allow siege to log in as a variety of different users.
- It fixes a bug in which cookies weren't sent if the domain had a leading dot.
- It also adds colorized output and color-coded error messages.
New in Siege 2.68 (Apr 29, 2009)
- This version adds support for digest authentication and includes several bug fixes. Users should see improvements in its ability to test HTTPS.
New in Siege 2.68 Beta 8 (Apr 15, 2009)
- Ugpraded utils/config.guess to more recent version
- Routine increment for src/version.c
New in Siege 2.68 Beta 5 (Feb 28, 2009)
- This release fixes a problem associated with proxy testing.
New in Siege 2.68 Beta 4 (Dec 30, 2008)
- This release fixes a problem in which some threads could hang while waiting for a read.