Added PNG signature checking, increased max header line length
Actually alpha libConfuse 2.x support.
Alpha libConfuse 2.x support. 304 + some typos bugfix from Cheuksan.
ziproxy-1.2 sources as it was released
Initial import.
Updated README about ImageQuality option
Added grayscale conversion possibility. Repaired possible data corruption if error/timeout occurs while transmitting data
Make ziproxy recognize background pictures in tables
Minor changes to prepare 1.2b release
Merged minor changes after 1.2b release
Added ChangeLog
Fixed a C incompatibility in ziproxy.c
Squashed some bugs I made by restructuring
Better JPEG2000 support, updated docs
GIF->PNG compression, alpha channel handling, advanced HTML modification for JP2
Got rid of compiler warnings for image.c
Better image type detection. Better HTML modification for JP2.
Catch image names with trailing spaces
Restructured HTTP code
Images can now be converted to JPEG2000
Bug fixes: http_headers initialization, image transformations
Fixed plain C incompatibilities
Repaired some configure bugs. Try PNG compression only if JPEG one is not satisfactory.
More bug fixes for image compression
Updated docs, fixed some bugs in JP2 HTML modification
Fixed bug in palette reduction alg
Added autoconf support
Release 1.3beta
Various things in image.c, fixed some comments everywhere
Little Gzip option change
Added AllowLookChange option
Apply AllowLookChange option to transparent PNGs too
fixed timeouts, little Gzip option change
released 1.3b
Serious bugs fixed related to gzip compression
Fixed ModifySuffixes same way as Gzip option
little changes to remove warnings, getting make
SSL fix
Better chunked behavior
Link statically with confuse by default
Uninitialized HTTP headers crash fix
Various bugfixes
Check your pg_hba.conf. For local connections there may be "trust" or "sameuser"...
I am in favor of this. Github provides anchors to every line and people got used...
Oh I did not realize postgres superuser must do it. Putting the hint to documentation...
There's possibility that since the versions are indexed sequentially, when scanning...
This for example took 30 seconds before: http://btc.yt/lxr/satoshi/ident?_i=a&_remember=1...
Improve Postgres performance