X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9B4FC3A4949 for ; Thu, 4 Nov 2004 21:02:31 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23007-03 for ; Thu, 4 Nov 2004 21:02:23 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id D82E23A497C for ; Thu, 4 Nov 2004 21:02:23 +0000 (GMT) Received: from [82.68.132.233] (82-68-132-233.dsl.in-addr.zen.co.uk [82.68.132.233]) by bayswater1.ymogen.net (Postfix) with ESMTP id 087DFA312C; Thu, 4 Nov 2004 21:02:22 +0000 (GMT) Message-ID: <418A986B.5040806@ymogen.net> Date: Thu, 04 Nov 2004 21:00:27 +0000 From: Matt Clark User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Foster Cc: PostgreSQL Performance Subject: Re: Restricting Postgres References: <003301c4c29a$f052d910$8300a8c0@solent> <418A915B.5060600@ethereal-realms.org> In-Reply-To: <418A915B.5060600@ethereal-realms.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/62 X-Sequence-Number: 9016 > These are CGI scripts at the lowest level, nothing more and nothing > less. While I could probably embed a small webserver directly into > the perl scripts and run that as a daemon, it would take away the > portability that the scripts currently offer. If they're CGI *scripts* then they just use the CGI environment, not Apache, so a daemon that accepts the inbound connections, then compiles the scripts a-la Apache::Registry, but puts each in a separate thread would be, er, relatively easy for someone better at multithreaded stuff than me. > > This should be my last question on the matter, does squid report the > proper IP address of the client themselves? That's a critical > requirement for the scripts. > In the X-Forwarded-For header. Not that you can be sure you're seeing the true client IP anyway if they've gone through an ISP proxy beforehand.