From: oes Date: Tue, 15 Oct 2002 12:38:56 +0000 (+0000) Subject: Added Microsuck faq; more detail for PHP problem X-Git-Tag: v_3_0_1~102 X-Git-Url: http://www.privoxy.org/gitweb/@user-manual@config.html?a=commitdiff_plain;h=56d9fbfa5f6223e30ae3c174de07482c48c68adf;p=privoxy.git Added Microsuck faq; more detail for PHP problem --- diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml index 49701b83..b483e38b 100644 --- a/doc/source/faq.sgml +++ b/doc/source/faq.sgml @@ -18,13 +18,13 @@ ]> + +I've noticed that Privoxy changes <quote>Microsoft</quote> to +<quote>MicroSuck</quote>! Why are you manipulating my browsing? + + + We're not. The text substitutions that you are seeing are disabled + in the default configuration as shipped. You have either manually + activated the fun filter which + is clearly labeled Text replacements for subversive browsing + fun! or you have implicitly activated it by choosing the + Advanced profile in the web-based editor. + + + @@ -1749,26 +1763,31 @@ every time I start IE. What gives? I get a completely blank page at one site. <quote>View Source</quote> - shows only: <markup><![CDATA[<html><body></body></html>]]></markup>. + shows only: ]]>. Without + Privoxy the page loads fine. - This is often the result of a webserver using - PHP that mishandles the request - Privoxy sends to not compress the content - (a PHP bug). + Chances are that the site suffers from a bug in + PHP, + which results in empty pages being sent if the client explicitly requests + an uncompressed page, like Privoxy does. + This bug has been fixed in PHP 4.2.3. - In a default configuration, Privoxy requests all - data be sent uncompressed. This is required for the page - filtering and other magic to work. In some rare cases, the browser and - webserver miscommunicate and the result is a totally blank page. The - suggested work around is to selectively turn off this feature for sites - that exhibit such behavior. Example section for user.action: + To find out if this is in fact the source of the problem, try adding + the site to a -prevent-compression section in + user.action: # Make exceptions for ill-behaved sites: # {-prevent-compression} .example.com + + If that works, you may also want to report the problem to the + site's webmasters, telling them to use zlib.output_compression + instead of ob_gzhandler in their PHP applications (workaround) + or upgrade to PHP 4.2.3 or later (fix). + @@ -1864,6 +1883,10 @@ FIXME: Commented out until we have something to put here. HB 03/18/02. Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: faq.sgml,v $ +Revision 1.61.2.22 2002/10/12 01:13:13 hal9 +Updates for demoronizer, more commentary on Radical profile, and update on +the srvany.exe/icon fix. + Revision 1.61.2.21 2002/10/10 04:09:35 hal9 s/Advanced/Radical/ and added very brief note.