GlimmerBlocker now uses less memory when using Snow Leopard on 64-bit capable hardware.

Fix hang when opening the Sys Prefs Panel

Use short http timeout when testing if the java server is running or not, as the standard 60 sec timeout (times 3 tries) will hang the Sys Prefs Panel for a looong time. Reported by Tom Gregory.

1. Fixes QuickTime Streaming: an extraneous CRLF sequence was added when sending http headers when GlimmerBlocker in advanced knew that the connection could not use keep-alive. Reported by Dominic Wäsch and Matthias Wallner.
2. Fix problem with uploads to MobileMe/iDisk which takes a long time. The upload would cancel because GlimmerBlocker would timeout waiting for a reply from the server when it was still sending the file. Reported by Andreas Maks.
3. Fix of keep-alive bug: if server said keep-alive was valid for 45 seconds, GlimmerBlocker would reuse the connection only in the next 45 milliseconds. This would make some sites slower.
4. Don't use keep-alive on an http-server connection when the full request body has not been read. This can happen when an upload is denied by the server, and GlimmerBlocker would try interpret the file as an http request.
5. Installer script: Better diagnostics for non-working java installations and permission problems on e.g. /Library/PreferencePanes. Thanks to Scott Collins for extensive testing.
6. Don't change content-type to text/html when a transform script has modified the content. This made it impossible to change javascripts without having Safari receive it as text/html, which it then would ignore and still use it as a script, but it was still wrong. If rule authors change the content-type, they must explicit set the content-type.

New feature for filter authors: Allow request scripts to set the 'Accept-Encoding' header to one of: null, empty string or (exactly) 'gzip'. No other values are allowed as GlimmerBlocker must be able to decode the response.