1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
Source: ziproxy
Section: net
Priority: extra
Maintainer: Marcos Talau <talau@users.sourceforge.net>
Build-Depends: debhelper (>= 9),
dh-autoreconf,
flex,
libgif-dev,
libjpeg-dev,
libpng-dev,
libsasl2-dev,
zlib1g-dev
Standards-Version: 3.9.6
Homepage: http://ziproxy.sf.net
Vcs-Git: https://anonscm.debian.org/git/collab-maint/ziproxy.git
Vcs-Browser: https://anonscm.debian.org/git/collab-maint/ziproxy.git
Package: ziproxy
Architecture: any
Depends: ${misc:Depends},
${shlibs:Depends},
adduser,
lsb-base (>= 3.0-10),
passwd
Description: 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.
|
