LiveZilla Live Help

You are here

Revision History - Windows

SafeSquid for Windows (Updated)

Critical Security BugFix:
The HTTP response header lines are in the usual text header format, which is: one line per header, of the form "Header-Name: value", ending with CRLF.
SafeSquid failed to correctly parse headers when the number of spaces or tabs between the ":" and the value was more than one.
One of the immediate mal-effects of this was non-detection of "Transfer-Encoding: chunked" headers.
This was largely witnessed with Microsoft IIS/6.0 webservers.

SafeSquid for Windows

  • Reduced CPU utilization.
  • Faster loading of dynamic pages.


SafeSquid for Windows

SafeSquid now offers better support for FTP over HTTP. A new built-in template handles user authentication for FTP sites that require user authentication. Reduced latency and overall response times.Security Bugfix to prevent faulty bypassing of content analysis of requests. Improved tolerance to slow response from heavily loaded, slow responding web-sites. Major improvements in ICAP, now allows use of multiple ICAP services. SafeSquid connects to each ICAP server in the list, until one modifies the request or response.

SafeSquid for Windows

Security Bugfix for a vulnerability that caused SafeSquid to terminate abnormally, when a remote client abruptly cancelled an incomplete Windows Integrated Authentication process.

SafeSquid for Windows

Bugfix for all errors reported since release of, aggregated in this release.
Known issue: Accesing some web-sites can cause NTLM authentication failures

SafeSquid for Windows 2012.0402.1834.2

Bugfix for errors in POST requests when NTLM / Negotiate authentication is enabled.
Bugfix for incorrect application of LDAP profiles when NTLM / Negotiate authentication is enabled.
Bugfix for improper CRLF line ending detection when URLBL files are edited in Windows Systems.
Speed enhancements - web responses not accompanied with content lenght headers took unpredictable time time open, if keyword filtering or rewrite document was enabled. This has been fixed.