Bug 641766 - RFE: compile privoxy with --enable-zlib
Summary: RFE: compile privoxy with --enable-zlib
Keywords:
Status: CLOSED DUPLICATE of bug 509557
Alias: None
Product: Fedora
Classification: Fedora
Component: privoxy
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-11 04:08 UTC by D. Wagner
Modified: 2010-11-02 08:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-02 08:30:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description D. Wagner 2010-10-11 04:08:14 UTC
Description of problem:

Could you modify the privoxy specfile so that it runs configure with the --enable-zlib option and rebuild the privoxy package?  It seems to make a significant difference for the better.

The current privoxy-3.0.16-2 RPM seems to be having trouble with many web sites: it causes web access to be very slow on some sites (the browser just hangs, but does not display the page).  When this happens, I observe the following messages spewed in /var/log/privoxy/logfile:

Info: Compressed content detected, content filtering disabled. Consider recompiling Privoxy with zlib support or enable the prevent-compression action.

This seems to affect high-volume sites like nytimes.com, amazon.com, etc.

So, I downloaded the privoxy-3.0.16-2 source RPM, and modified the spec file to compile with "configure --enable-zlib".  After that change, all the problems went away, and web access is snappy again.  With this change, everything seems to work fine for me.  Therefore, I suggest modifying the privoxy spec file for the standard privoxy RPM.  It's a simple one-line change to the spec file:

-%configure
+%configure --enable-zlib

Comment 1 Petr Pisar 2010-11-02 08:30:47 UTC

*** This bug has been marked as a duplicate of bug 509557 ***


Note You need to log in before you can comment on or make changes to this bug.