Version: 2.2.33, created 2008-02-10
Version: 2.2.32, created 2008-02-07- Support for Apache Tomcat have been added.
Version: 2.2.31, created 2007-12-27- The previous release was incorrectly packaged, so a new release has been issued to clear up some confusion.
Version: 2.2.30, created 2007-12-13- A server in a clusters with Capacity set to 0 (zero) now acts as a stand by server and will not get any traffic until all other servers are offline.
Version: 2.2.29, created 2007-11-28- Fixes to status page. An error could randomly occure on the status page.
- Resource fix on status page. The browser would load the page slower and slower.
- Improved error message.
Version: 2.2.28, created 2007-04-12- Fixes SSL issues
- Adds function for redirecting 302 answers to HTTPS, when the webserver tries to move a session to HTTP.
- Failover tests for clusters improved
Version: 2.2.27, created 2007-04-12- New version includes libssl32.dll in installation package
Version: 2.2.26, created 2007-04-09- Upgraded OpenSSL to latest version 0.9.8e
Version: 2.2.25, created 2007-02-20- Fixed bug where under certain circumstances, a server was flagged as offline after a single failed connection, instead of honoring the setting that defines how many failed connections should be accepted before a server is considered offline.
Version: 2.2.24, created 2007-02-06- Increased the verification time of servers in a cluster to 2 seconds, if the server fails to respond within 2 seconds, it's considered to be offline.
Version: 2.2.23, created 2007-01-30- Improved logging for servers in server cluster, detailed information is now placed in the log, explaining when and why a server comes and goes.
Version: 2.2.22, created 2006-11-15- Corrects issue where log file updates would stop once the log file grew beyond a certain size.
Version: 2.2.21, created 2006-10-03- IIS returns HTTP/1.1 on requests for HTTP/1.0 information, this could previously be misinterpreted as a keep alive connection, making browsers running through squid proxies miss certain requests. Now, OctaGate Switch requires that both request and response use HTTP/1.1 for keep alive to be used.
Version: 2.2.20, created 2006-09-20- This version allows more Keep-Alive connections, as long as the server isn't overloaded.
Version: 2.2.19, created 2006-08-22- Compressed content sent to browsers using a squid proxy would sometimes work incorrectly - compressed data is no longer sent to users behind squid proxies.
Version: 2.2.18, created 2006-05-22- Made adding slash to virtual paths that lack slashes optional on a per virtual path basis.
Version: 2.2.17, created 2006-05-01- We've made "use "X-Forwarded-For" for session key" optional, due to issues with proxy caches - namely squid. This only effects users who have been running load balancing. X-Forwarded-For is required if another web-frontend product is used in front of OctaGate Switch.
Version: 2.2.16, created 2006-04-16- Fixed issue where a missing end slash would make a virtual path work incorrectly
Version: 2.2.15, created 2006-04-07- Various minor bugs corrected.
Version: 2.2.14, created 2006-04-07- 49,7 day bug resolved - upgrade strongly recommended.
The third party tool that we are using for the web interface had a bug where the web interface wouldn't work once the server (the actual machine, not just the OctaGate Switch Service) had been running for more than 49,7 days. OctaGate Switch would function properly, but the administration interface would be unavailable.
This has been a major issue for us, and we strongly recommend that you upgrade.