From 166f65942bb0c1185080edd5dd781b3045364acf Mon Sep 17 00:00:00 2001 From: hal9 Date: Tue, 13 Aug 2002 00:10:38 +0000 Subject: [PATCH] Add faq to troubleshooting re: blank page syndrome, ie {-prevent-compression}. --- doc/source/faq.sgml | 32 ++++++++++++++++++++++++++++++-- 1 file changed, 30 insertions(+), 2 deletions(-) diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml index c6eaf91e..fdeb0a89 100644 --- a/doc/source/faq.sgml +++ b/doc/source/faq.sgml @@ -24,7 +24,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: faq.sgml,v 1.61.2.14 2002/08/07 02:53:43 hal9 Exp $ + $Id: faq.sgml,v 1.61.2.15 2002/08/10 11:34:22 oes Exp $ Copyright (C) 2001, 2002 Privoxy Developers See LICENSE. @@ -72,7 +72,7 @@ -$Id: faq.sgml,v 1.61.2.14 2002/08/07 02:53:43 hal9 Exp $ +$Id: faq.sgml,v 1.61.2.15 2002/08/10 11:34:22 oes Exp $ + +I get a completely blank page at one site. <quote>View Source</quote> + shows only: <markup><![CDATA[ +<html><body></body></html>]]></markup>. + + This is usually the result of a webserver that mishandles the request + Privoxy sends to not compress the content. + + + 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: + + + # Make exceptions for ill-behaved sites: + # + {-prevent-compression} + .example.com + + +