Return-Path: Delivered-To: apmail-httpd-docs-archive@www.apache.org Received: (qmail 10413 invoked from network); 1 Aug 2007 15:40:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Aug 2007 15:40:22 -0000 Received: (qmail 60428 invoked by uid 500); 1 Aug 2007 15:40:21 -0000 Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 60404 invoked by uid 500); 1 Aug 2007 15:40:20 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: docs@httpd.apache.org List-Id: Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 60393 invoked by uid 99); 1 Aug 2007 15:40:20 -0000 Received: from igron-1.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2007 08:40:20 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [64.202.165.182] (HELO smtpauth02.prod.mesa1.secureserver.net) (64.202.165.182) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 01 Aug 2007 15:39:49 +0000 Received: (qmail 22748 invoked from network); 1 Aug 2007 15:39:49 -0000 Received: from unknown (24.15.193.17) by smtpauth02.prod.mesa1.secureserver.net (64.202.165.182) with ESMTP; 01 Aug 2007 15:39:49 -0000 Message-ID: <46B0A945.6040606@rowe-clan.net> Date: Wed, 01 Aug 2007 10:39:49 -0500 From: "William A. Rowe, Jr." User-Agent: Thunderbird 1.5.0.12 (X11/20070719) MIME-Version: 1.0 To: docs@httpd.apache.org Subject: Re: Ban the phrase "reverse-proxy"? References: <46B00740.7070009@rowe-clan.net> <20070801115035.GA32156@eilebrecht.net> <90982F8F-D639-464E-AD76-7F92081DCCBD@codefaktor.de> In-Reply-To: <90982F8F-D639-464E-AD76-7F92081DCCBD@codefaktor.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org >>> What would folks say to renaming all occurances of "reverse proxy" >>> to say "gateway" in our documentation? jean-frederic clere wrote: > I am not sure that is a good idea see > http://en.wikipedia.org/wiki/Reverse_proxy read and contrast to http://en.wikipedia.org/wiki/Gateway_%28telecommunications%29 which is equivalent to http://en.wikipedia.org/wiki/Gateway_%28computer_networking%29 Erik Abele wrote: > On 01.08.2007, at 13:50, Lars Eilebrecht wrote: > >> "Reverse Proxy" is a commonly used term, and I don't see a reason >> why we should use something else. > > and is there a special reason for the proposed change or just > über-correctness? :) several reasons; * Reverse-proxy is somethign of a double negative, making the term impossible to 'visualize' - Even "Content-proxy" would be clearer than 'Reverse'. We aren't sending requests from the back end server to the client, that would be "reversing" the connection or proxy. * it doesn't conform to proxy semantics from an HTTP server point of view. RFC spelled out for a very long time that proxy [...] A "transparent proxy" is a proxy that does not modify the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is a proxy that modifies the request or response in order to provide some added service to the user agent, such as group annotation services, media type transformation, protocol reduction, or anonymity filtering. gateway A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway. * the httpd developers freely admit the way things are named is often crusty and could use improvement. At the minimum, I plan to notate "reverse-proxy (e.g. gateway server)" liberally throughout the explanation pages of the module and guides. Bill --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org