31.3.2008

• Proxy authentication would bring access denial if such was not requested by Ziproxy (unnecessary authentication sent by user).
  Now it is simply ignored and access is normal.
• Ziproxy did not send the proper URL to the server (so it failed) when connecting to another proxy and the client accessed Ziproxy in transparent proxy mode.
  Fixed.

10.3.2008

• When non-processable (htmlopt etc) data came already gzipped, Ziproxy tried to load it all into memory, then it recompressed again.
  Now it streams that directly, unmodified. Should improve latency in certain cases.

29.1.2008

• Rewritten and much improved JPEG 2000 support. It's much faster now and quality of the JPEG 2000 pictures are much, much better.
  Many JP2-related options were added (although the defaults are quite reasonable).
  Everyone are invited to give JPEG 2000 a try!
  Note: JPEG2000 requires from the client either one of the following:
  
  • Browser with native JPEG2000 support (such as Konqueror) OR
  • Browser with installed JPEG2000 plug-in (there are for Firefox, possibly others) OR
  • To install Ziproxy at the client side in order to convert JPEG2000 back to JPEG
  Certain plug-ins/browsers (specially old versions) do have an incomplete JPEG2000 support and may break the pictures, or may even crash.
• Changed default configuration file to /etc/ziproxy/ziproxy.conf
  This was needed in order to have a standard directory for the other (optional) configuration files.
• New example configuration files added.
• Manpages for ziproxy and ziproxylogtool added.
• Added a mechanism to "exempt" certain URLs from processing (broken webservers, broken sites etc).
• The basic authentication routines were mostly rewritten (code reorganization / speedup).

16.1.2008

• Changed default configuration file from /etc/ziproxy to /etc/ziproxy/ziproxy.conf
  There are other (optional) configuration files that had no standard place to be, now their home is /etc/ziproxy
• New example configuration files included (which now has a suggested location of /etc/ziproxy/).
• Manpages for ziproxy/ziproxylogtool added. A contribution from Marcos Talau.
• Now it's possible to exempt certain URLs from Ziproxy processing (in case of malformed HTTP data, Ziproxy bugs or simply because compression is not desired for a specific location).
  It has a simple pattern-matching provision, with "*".
  New option: URLNoProcessing
• The (basic) authentication routines were mostly rewritten. Mostly for code reorganization, but should be much faster as side-effect (only noticeable if one has many, many users).

7.1.2008

• Much faster processing (JP2 is still heavier to process than JPEG).
• Supports both compression and decompression. It's possible to process incoming JP2 pictures now.
• Compression level is no longer rate-based, but quality-based such as JPEG.
• Supports YUV color model now. Previously only RGB and monochrome.
• Supports per-channel resulution setting. Previously only 8 bit per channel.
• Supports per-channel sampling resolution. Previously there was no such support.
• Added provisions for what one may call "Ziproxy tunnel mode" locally converting JP2 back to (high quality) JPEG, so clients with no JP2 support may take advantage of that format still.

15.12.2007

5.12.2007

• The following bugs are now fixed:
  
  • Fixed broken user pipe detection while transferring unprocessed stream-to-stream.
  • When server breaks the connection, ziproxy immediately interrupted the transfer at client's side.
    Now it will send the remaining data to the client.
    The previous behavior could bring premature disconnections.
  • Content-Length wasn't being removed while stream-to-stream gunzipping. Fixed.
  • Ziproxy crashed when AccessLogFileName wasn't defined. Fixed. This bug appeared in 2.4.1 version.
• Improvements:
  • Now (debug) log provides each line with the PID of the specific process servicing the specific HTTP request.
    Previously it merely provided the base Ziproxy process, what is pretty much useless in daemon mode and made sense only while using (x)inetd, or in pre-1.9.0 versions.
  • Stream-to-stream (no further processing) routines were rewritten and are >100x times faster now. This may bring noticeable difference in cases where outgoing data is something like 10 Mbps or more.
  • Added access log flag 'W'.

23.11.2007

• The following bugs are now fixed:
  
  • When decompressing jpeg incomplete files, ziproxy process crashes (busy loops) until it timeouts.
    This is a very old bug, finally fixed.
• New features/options:
  • New option: BindOutgoing
    If you have a huge number of users behind Ziproxy
    this option probably makes sense for you.
  • New option: AccessLogUserPOV
  • Added new xml types as (gzip) compressible *1.
    Added 'pdf' and 'tar' as compressible application types.
  • Added access log support for interrupted/timeouted transfers.
    Added access log flags 'Z' (timeout)
    and 'B' (broken pipe, interrupted)

7.11.2007

• The following bugs are now fixed:
  
  • In certain cases, random junk was appended at the top of html file.
  • Trivial overflow problem which gave false positives for "gunzip threshold limit".
  • Ziproxy tried to load into memory, data types which are not supposed to be processed, thus adding unnecessary latency.
  • When config file was empty, the following error occurred: ERROR: Invalid parameter --> <empty>
  • Intermitent bug when gzip-streaming pages (random numbers appeared in the body of the page, mixed with the content).
    This bug appeared in 2.3.5_BETA.
  • Misc fixes to HTMLopt: maps.google.com and www.hotmail.com seem to work after optimization, now.
• New features/options:
  • New option: MinUncompressedGzipStreamEval
  • Added support for javascript files as text/javascript (relevant only when JS optimization is enabled).
  • HTMLopt: Now tests whether text/html is indeed html.
    In practice, it's not always the case: certain (or most?) servers send pure (non-html encapsulated) JS or CSS and the resulting data will likely end corrupted.

26.10.2007

• Replaced libconfuse with qparser (built-in config parser), thus that library is no longer used.
• New option:
  WA_MSIE_FriendlyErrMsgs (workaround for MSIE bug),
• Added (limited) support for partial data download (Content-Range, Range).
• Added gzip/gunzip stream-to-stream support. Appliable when no other optimizations are requested/viable.
• Now logs always report gzipped transfers new sizes.
• Changed some defaults to more sensible values.

• Broken gzip were not being uncompressed (that's ok) but Ziproxy attempted to recompress those again. Fixed.
• Requests were broken when in transparent proxy mode _and_ the client explicited the port. Fixed.
• Fixed missing includes and certain inconsistencies in the source code. That could (or did) prevent compilation in certain OSes.
• Fixes x86_64 (and possibly other arches) parsing problems (see new features: qparser).
• MinTextStream was using the decompressed size, what is senseless if the data came pre-compressed by the remote server. Fixed.
• Many other misc bugfixes.

13.9.2007

• New: support for remote host-side gzip compression.
• Fixed compatibility code for IPv4-only OSes.
• Slightly more informative error pages.
• A couple of bugs in HTMLopt were fixed
  (still HTMLopt is far from being production quality).
• New options:
  • AllowMethodCONNECT
  • OverrideAcceptEncoding
  • MaxUncompressedGzipRatio
  • RedefineUserAgent
  • DecompressIncomingGzipData
  • ProcessHTML_TEXTAREA
• Miscellaneous fixes and changes in the HTTP routines.

8.5.2007

• Some files with too many headers were not loadable (typically some wikipedia.org pictures). Fixed.
• HTMLopt: Fixed commented (escaped, in a way) CDATA XML tag which was being removed.
• HTMLopt: Fixed trailing trash in html/javascript/css which was being removed.
• Ziproxylogtool: Added internal caching (about 4.5x faster in large logs now).
• Added README.tools.

19.12.2006

18.12.2006

• Ziproxy Log Tools. Even includes output to fancy HTML.

• ConventionalProxy
• Address
• Nameservers *1

• HTTP 302/304 bug (prevented youtube.com from working properly) *1
• Ziproxy was passive when collecting zombie children *1
• AllowLookChange has incorrect default
• Standalone javascript files weren't being compressed *2

2.9.2006

26.7.2006

29.6.2006

• PDF, RTF (and shortnamed mime types in general) now gzip correctly.
• Changes to the rpm specfile allowing of static binary generation.

18.5.2006

• Monolithic architeture. Netd is obsolete, there's only the "ziproxy" binary now, which operates in both daemon mode and [x]inetd mode.
• Transparent proxy mode, self explanatory. Option: TransparentProxy
• Detailed access log. Provides, among other informations, compression statistics. Option: AccessLogFileName
• New tuning parameter. Option: MinTextStream
• New command line parser. Type "ziproxy --help" to get the idea.

20.11.2005

15.11.2005

• New feature: Authentication support. Contributed by Roman Korolyov.

18.7.2005

• New feature: Preemtive hostname resolver.
• Error messages are now customizable. Examples included.

• Fixed transparent gif misdetection (AllowLookChange=false).
• Fixed bug which prevented compilation with JPG2k support.
• Ziproxy tried to connect only to the first IP from a resolved hostname (some few sites returned "connection refused"). Now fixed.
• Misc changes/fixes to RPM specfile.
• Fixed compilation libpng-related warnings.

17.6.2005

• Added new options to the config file: ProcessJPG, ProcessPNG, ProcessGIF.
• Added initscript, for convenience.
• Added RPM specfile.
• Improventes to the example config file.

• Fixed: Random crashes in Ziproxy process.
• Fixed: The "socket busy" bug.

12.6.2005

From: Juraj Variny <xxxx@xxxxxxx>
To: Daniel Mealha Cabrita <xxxxx@xxxxxx>
Date: Sun, 12 Jun 2005 13:04:48 +0200
Subject: [Ziproxy-users] Re: bugfix for Ziproxy

I did not asked for uber-clean patches. Correct and useful ones are
sufficient. :o)

Thus, your patch was committed into CVS and you are now admin of the project.

Good luck!

Juraj

On Saturday 11 June 2005 21:45, you wrote:
>       I'm sending you the patch, attached. It's a quick-and-dirt fix actually,
> but the only (rare) crashes I've had afterwards were libungif-related only.
>
>       If you still feel it's ok to transfer the project to my hands, my
> sourceforge login is: dmcabrita.
>
>
> .dan

30.9.2004

• Removed chunked encoding issue when accessing some servers.
• LibConfuse is linked statically by default.

6.8.2004

14.7.2004

• Better libconfuse detection (using confuse-config from confuse 2.3).
• More permissive parsing of headers (sites like bestbuy.com didn't work).
• Images or compressible content that exceed MaxSize are now forwarded unchanged instead of error.
• Fixed HTTPS behavior if NextProxy is set.

10.1.2004

24.11.2003

23.11.2003

29.10.2003

• New autotools-based installer, configure script with bunch of convenient options. No more Makefile editing! In case something goes wrong, there's still plain Makefile in src/ .
• GIF->PNG lossless image conversion where appropriate, with transparency preserved.
• HTML modification is considered obsolete and turned off by default.
• JPEG2000 mode (compile-time option). It is intended to work together with JP2 plugin for MSIE (see below), while still fully compatible with non-JP2 browsers.
• HTTP/1.0 Simple Response support, with image header detection and compression.
• Many bugfixes (better timeout behaviour, PNG reading bug, LogPipe set in incompatible mode by default, ...).

16.8.2003

9.8.2003

• Some or all pictures may be converted to grayscale. This improves visual quality, while keeping file size.
• If you are not willing to start netd with IP address each time you're dialing, you may now use range of IP addresses in OnlyFrom option.
• libConfuse 2.x support (don't forget to set it in Makefile).

23.7.2003

Sourceforge.net
Ziproxy file releases

• libungif
• libpng
• libjpeg-6b
• zlib
• libjasper
  (required if JPEG2000 support is to be enabled)

Ziproxy output to my browser is interleaved with logging output, i.e. things like "[1234] Finished." appear in some web pages!

Are you using xinetd with ziproxy? Then disable LogPipe option in ziproxy.conf. Or disable both LogPipe and LogFile options to turn off the logging completely. Piping the logging output through other program is supported only if you use netd. It's my mistake I kept these options on in default ziproxy.conf, with too terse disclaimer.

MSIE setup for ziproxy

To get IE accepting gzipped data, under Internet Options/Advanced tab check option ``Use HTTP/1.1 extensions when using proxy''.

Some pictures have inapropriate background color

Some transparent GIFs/PNGs are displayed with incorrect background. It's because JPEG can't store transparency information, and background color information is "out there" in HTML. With AllowLookChange option you can make ziproxy avoid these images.

ziproxy seems running, but I can't login/run other programs on that remote machine!

For every HTTP request, new ziproxy process is started. In case of intensive parallel downloading/mirroring (for example, with HTTrack or wwwoffle -fetch), number of processes may reach maximal user processes limit set by administrator. To avoid the problem, set subsequent limit for netd using limit(csh) or ulimit(bash) shell command.

• ziproxy-users: discussion about ziproxy compilation and usage, usage questions, feature requests, bug reports
• ziproxy-announce: ziproxy announcements (read-only)
• ziproxy-devel: developers' discussion, submitting patches

If you encounter problem with this webpage (broken link, information missing here, errors etc), you may contact the maintainer directly.