ziproxy 3.3.1-2.1ubuntu1 source package in Ubuntu

Changelog

ziproxy (3.3.1-2.1ubuntu1) groovy; urgency=medium

  * Fix FTBFS with gcc 10.

 -- Michael Hudson-Doyle <email address hidden>  Mon, 05 Oct 2020 13:49:21 +1300

Upload details

Uploaded by:
Michael Hudson-Doyle
Uploaded to:
Groovy
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
net
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Groovy release universe net

Downloads

File Size SHA-256 Checksum
ziproxy_3.3.1.orig.tar.bz2 268.9 KiB c39c6148840cdaa867d4dd3ad41d39be345494b2048b86ec899d0c075e56874d
ziproxy_3.3.1-2.1ubuntu1.debian.tar.xz 7.5 KiB 25ba213137b59b19373ae67355cf3939f87adc0baeda7d8d14b689620ada01d0
ziproxy_3.3.1-2.1ubuntu1.dsc 2.0 KiB a1f3a0b8c99b5c5472310c27d8142017af4edcb1127b6916be636ebc6e31dc53

View changes file

Binary packages built by this source

ziproxy: compressing HTTP proxy server

 Ziproxy is a forwarding, non-caching and compressing HTTP proxy server.
 Basically it squeezes images by converting them to lower quality JPEGs
 and compresses (gzip) HTML and other text-like data. It also provides
 other features such as: HTML/JS/CSS optimization, preemptive hostname
 resolution, transparent proxying, IP ToS marking (QoS), Ad-Blocker,
 detailed logging and more.
 .
 Ziproxy may be installed in a number of different ways. Most common
 setup modes:
  1) As a remote proxy (by far, the most commonly used setup)
     Ziproxy accesses the remote www servers through a fast link,
     compresses the data, then send it to the client through a slow link.
     In such setups there's no additional software required by the client,
     Ziproxy acts much as a common network proxy.
  2) As a local and remote proxy
     Similar to setup #1, except that the client also runs its instance of
     Ziproxy. Although Ziproxy does not require a Ziproxy-specific client,
     there are circumstances where is desired to run Ziproxy-as-a-client:
       * Client does not support JPEG 2000.
       * Client supports JPEG 2000 but it is buggy and/or slow.
       * Client does not support gzip.
       * Need to support both JPEG 2000 and standard JPEG at the same proxy.

ziproxy-dbgsym: debug symbols for ziproxy