Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 9704 invoked from network); 13 Mar 2008 16:00:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Mar 2008 16:00:09 -0000 Received: (qmail 37078 invoked by uid 500); 13 Mar 2008 15:59:55 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 37063 invoked by uid 500); 13 Mar 2008 15:59:55 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 37052 invoked by uid 99); 13 Mar 2008 15:59:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Mar 2008 08:59:55 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jslive@gmail.com designates 216.239.58.184 as permitted sender) Received: from [216.239.58.184] (HELO gv-out-0910.google.com) (216.239.58.184) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Mar 2008 15:59:15 +0000 Received: by gv-out-0910.google.com with SMTP id r4so1109612gve.23 for ; Thu, 13 Mar 2008 08:59:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=1wqp5H+k1p6csv5ZvT9PSZF1VSfA9oNHCHxBwOo0E5g=; b=Zg35Zi03FidlYdOLvdDVSfv5n/qsxuFjzkuiu46ZRZq4+ocjLAAayFQJwsbOsTHfg4mhtPiolMaHS98TgW9uLMk4ZHF7MWonPhF3gxm5P8WSeabcz4+5E/UT2mPt+BRyFNLkC6kTmePkTel4m0orNpTXbbvPbbh8MmrpeQyJFE0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=L6gcXYv6pKi1/CFp8V0BxRwLYCe5ble//27Px28AQodP6YUukZgFj3sFvfjyw0YNw4UNqbtEoskTEH+CxP8Dni9grAr83Rjwd12caFcODC1e0PcSHLXNMxicHpWrl8J9PlBK+ur8ah7c6NSXiu/EZ1CYn4Lf/cPOqLHKKG6CUi8= Received: by 10.150.152.17 with SMTP id z17mr5527074ybd.37.1205423964198; Thu, 13 Mar 2008 08:59:24 -0700 (PDT) Received: by 10.150.177.5 with HTTP; Thu, 13 Mar 2008 08:59:24 -0700 (PDT) Message-ID: Date: Thu, 13 Mar 2008 11:59:24 -0400 From: "Joshua Slive" Sender: jslive@gmail.com To: users@httpd.apache.org In-Reply-To: <200803131643.25977.aleksandersen+apache.org@runbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200803131643.25977.aleksandersen+apache.org@runbox.com> X-Google-Sender-Auth: 9c8680eef8eac317 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Header unset Server On Thu, Mar 13, 2008 at 11:43 AM, Daniel Aleksandersen wrote: > Hi list, > > The below option spesified in the document_root/.htaccess have no effect. > Should it work? It may be my shared hosting enviroment that is messing up > this one. I see that all headers still have "Server: Apache". > Header unset Server > Header unset Content-Location Because of where mod_headers acts in the request processing pipeline, it is not possible to modify or unset many of the standard headers apache uses for protocol compliance. I wouldn't be surprised if the above two were in that category, although I haven't checked. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org