New in version 3.0.7
October 13th, 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 version 3.0.6 (January 9th, 2014)
- Updated to include proxy directives
New in version 3.0.6 Beta 2 (November 1st, 2013)
- Added support for HTTP-303.
New in version 3.0.5 (October 18th, 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 version 3.0.4 Beta 1 (September 13th, 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 version 3.0.3 (August 20th, 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 version 3.0.3 Beta 3 (July 31st, 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 version 3.0.3 Beta 2 (July 26th, 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 version 3.0.2 (July 19th, 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.