From 66cb7e1f56fd74942daf7b789c5f4ac66f1f64d9 Mon Sep 17 00:00:00 2001
From: hal9 <hal9@users.sourceforge.net>
Date: Thu, 26 Sep 2002 01:22:45 +0000
Subject: [PATCH] Small additions for LAN setup, content-cookies/SSL, and FTP
 non-support.

---
 doc/source/faq.sgml | 47 +++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 45 insertions(+), 2 deletions(-)

diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml
index 0c112ca6..ab6b727f 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.18 2002/08/14 16:39:37 hal9 Exp $
+ $Id: faq.sgml,v 1.61.2.19 2002/08/25 23:31:56 hal9 Exp $
 
  Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
  See LICENSE.
@@ -72,7 +72,7 @@
  </subscript>
 </pubdate>
 
-<pubdate>$Id: faq.sgml,v 1.61.2.18 2002/08/14 16:39:37 hal9 Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 1.61.2.19 2002/08/25 23:31:56 hal9 Exp $</pubdate>
 
 <!--
 
@@ -853,6 +853,29 @@ with a browser? Does that not raise security issues?</title>
  all browsers on the network then to use this address and port number.
 </para>
 
+<para>
+ Alternately, you can have <application>Privoxy</application> listen on 
+ all available interfaces:
+</para>
+
+<para>
+ <screen>
+  listen-address    :8118</screen>
+</para>
+
+<para>
+ And then use <application>Privoxy's</application> 
+ <ulink
+ url="../user-manual/config.html#PERMIT-ACCESS">permit-access</ulink> 
+ feature to limit connections. A firewall in this situation is recommended 
+ as well.
+</para>
+
+<para>
+ The above steps should be the same for any TCP network, regardless of
+ operating system.
+</para>
+
 <para>
  If you run <application>Privoxy</application> on a LAN with untrusted users,
  we recommend that you double-check the <ulink
@@ -1387,6 +1410,14 @@ ads used to be. Why?</title>
  for efficiency reasons, which exposes them to the full power of 
  <application>Privoxy</application>'s ad blocking.
 </para>
+<para>
+ <quote>Content cookies</quote> (those that are embedded in the actual HTML or
+ JS page content, see <literal><ulink
+ url="../user-manual/actions-file.html#FILTER-CONTENT-COOKIES">filter{content-cookies}</ulink></literal>), 
+ in an SSL transaction will be impossible to block under these conditions. 
+ Fortunately, this does not seem to be a very common scenario since most 
+ cookies come by traditional means.
+</para>
 
 </sect2>
 
@@ -1661,6 +1692,13 @@ every time I start IE. What gives?</title>
   so do not configure your browser to use <application>Privoxy</application>
   as an FTP proxy. The same is true for any protocol other than HTTP or HTTPS.
  </para>
+  <para>
+  Most browsers understand FTP as well as HTTP. If you connect to a site, with
+  a URL like <literal>ftp://ftp.example.com</literal>, your browser is making
+  an FTP connection, and not a HTTP connection. So while your browser may 
+  speak FTP, <application>Privoxy</application> does not, and cannot proxy 
+  such traffic.
+ </para>
 </sect2>
 
 <!--   ~~~~~       New section      ~~~~~     -->
@@ -1816,6 +1854,11 @@ 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.19  2002/08/25 23:31:56  hal9
+Fix one grammatical error. Add brief FAQ relating to tranparent proxies (ie
+port 80 setting). Add FAQ on effects of Privoxy on downloaded files
+(especially filtering).
+
 Revision 1.61.2.18  2002/08/14 16:39:37  hal9
 Fix wrong tag on FAQ addition.
 
-- 
2.50.1