Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <430F55E1.4080806@modperlcookbook.org>
Date: Fri, 26 Aug 2005 13:48:17 -0400
From: Geoffrey Young <geoff@modperlcookbook.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040927
MIME-Version: 1.0
To: Perrin Harkins <perrin@elem.com>
CC: dev@perl.apache.org
Subject: X-Powered-By (was Re: survey)
References: <AD29A02FF1E26647BACE78F60B7A5953182C3E@exchange.brunico.com>
 <1125075334.6286.45.camel@localhost.localdomain>
In-Reply-To: <1125075334.6286.45.camel@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Perrin Harkins wrote:
> On Fri, 2005-08-26 at 12:47 -0400, Adam Prime x443 wrote:
> 
>>PHP uses:  X-Powered-By: PHP/4.3.11
>>
>>To effectively bypass the front end server problem.
> 
> 
> We decided not to do that, since it's intrusive.

I think I remember the discussion, even being against it :)

however, I'm not sure that I made the connection between that header and
backend-proxy statistics...

so, I might be in favor of adding it if

  - we can prove netcraft uses this to determine a php-driven site.  if not
that puts us on an even playing field

  - we can coerce netcraft into translating that into mod_perl usage

  - we have it obey the ServerTokens directive, so if mod_perl doesn't show
up in the server string neither does this

  - we think it actually matters - the vast majority of mod_perl sites out
there won't have this due to software versions, even if we backport it to
mp1 and make a mp1 release, so I'm not sure it would impact our numbers all
that much.

thoughts?

--Geoff

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org