Stas Bekman wrote:
Philippe M. Chiasson wrote:
Perrin Harkins wrote:
On Thu, 2005-01-06 at 13:49 -0800, Philippe M. Chiasson wrote:
[...]
I can understand the concerns. I am looking for a suggestion that would put us
on equal footing with what php is doing.
It seems PHP has a flag expose_php that is on by default. So I guess we could just
do the same:
ModPerlExpose On|Off
And have it default to On as well? Would that accomodate people's concerns ?
As it's HTTP-specific, I'd rather call it:
ModPerlHTTPExpose On|Off
not to mislead users.
How about this instead:
PerlOption (+|-)ExposeHttp or PerlOption (+|-)HttpExpose
That's better, but in either case it should be HTTP (not Http)
But on the other hand I tend to agree with Joe Orton, that may be trying to copy that "feature" from php is not the best idea, as adding an extra mostly useless payload to each response is not the best thing to do. Especially if ServerToken is already set to full.
So my latest vote on this is +0.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
