Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E8F64DC44 for ; Sun, 16 Sep 2012 07:26:21 +0000 (UTC) Received: (qmail 9987 invoked by uid 500); 16 Sep 2012 07:26:19 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 9257 invoked by uid 500); 16 Sep 2012 07:26:11 -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 9217 invoked by uid 99); 16 Sep 2012 07:26:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Sep 2012 07:26:10 +0000 X-ASF-Spam-Status: No, hits=4.7 required=5.0 tests=FREEMAIL_FORGED_REPLYTO,FSL_FREEMAIL_1,FSL_FREEMAIL_2,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.139.212.188] (HELO nm29.bullet.mail.bf1.yahoo.com) (98.139.212.188) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 16 Sep 2012 07:25:59 +0000 Received: from [98.139.215.143] by nm29.bullet.mail.bf1.yahoo.com with NNFMP; 16 Sep 2012 07:25:38 -0000 Received: from [98.139.212.224] by tm14.bullet.mail.bf1.yahoo.com with NNFMP; 16 Sep 2012 07:25:38 -0000 Received: from [127.0.0.1] by omp1033.mail.bf1.yahoo.com with NNFMP; 16 Sep 2012 07:25:38 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 436458.67469.bm@omp1033.mail.bf1.yahoo.com Received: (qmail 82272 invoked by uid 60001); 16 Sep 2012 07:25:38 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1347780338; bh=rwuTZymZeo86UPLSp3/+efPr1fxMrFqRw4Mn8qnEclo=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=D0MGerWsHkac0LdSGF5tmj3SoYKzf6Mwf6luusgwJqZ+CM6gSJZGnqwITdVKv7BjlvgNL5mKO4xNCnB7NmHAjfQEeEfwUKN3rGRvSTHRXwi6Em9ZOHLdeGILcDGx0u9b+VP304LjAuDnM3MPpWmgnUTQ6cw8LFocWcH8KJfA+qk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=WZsqffPrpcyrn5WacaOrVdicnACfnYyYYeSoPrTa2AHkgmw3GxQv8aE1Fe9YnGJaMAT+peDeyHgPaBPncwEOJP1cxO730gDhCN0/2aflq3SjZhKaSH2aNUiMB3CbywSVA2VNGSZtBf5P/0og+yU3q+47CFYvwwwJl416eM4yAwY=; X-YMail-OSG: WSYw1ZAVM1kzVIK5bNoqci40KNsxRNAuqMlylSYeUOjdJQG lJgk3xeU4IHacE8qlok2Ep4FJsCk0GcoIVWm5SD5HlKT89mqTPFqVBuy.Rsf 8uij3UPA7gvSEDCGRFflxdAQCvGO8Fgnax2y3qthFr_PRSUEcs4CCbNDNhuy VT_IHtW1Diw9k3sLh2dm8i8Mrhu90qZ5lwlZ2QesWwPW9Wkj25QzzFOSBFoN aG0symPw18vf1i06ISJrH3tp7giNdequV2jovLKDZr78UU8vPF6GTF81wNOp 1yODq9uam6fSYA.NmU4sJGXv.PAHRB0eA8_kmMQ9aa6bGKEOOaZBhEgmHoT1 9.eFTKLRndn935eXsFhRD925PMzNh5MXMitSzkhTObrGTaq8Ogjgpy.jqH34 0TTts7rLVZhKDJFPKCj0SEHlKvS6tR_fRyeiMgw-- Received: from [38.104.195.22] by web140706.mail.bf1.yahoo.com via HTTP; Sun, 16 Sep 2012 00:25:38 PDT X-Mailer: YahooMailWebService/0.8.121.416 Message-ID: <1347780338.70085.YahooMailNeo@web140706.mail.bf1.yahoo.com> Date: Sun, 16 Sep 2012 00:25:38 -0700 (PDT) From: Crne We Reply-To: Crne We To: "users@httpd.apache.org" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-637016289-605019937-1347780338=:70085" Subject: [users@httpd] 403 forbidden ---637016289-605019937-1347780338=:70085 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Env: Windows/apache 2.2=0A=A0httpd.conf: =A0 Forward proxy configuration wi= th Basic auth.=0A=0A=0AWhy would httpd respond with 403 for a valid http re= quest?=0AThere are no special restrictions configured besides basic Proxy s= etup on top of standard httpd.conf (after clean install). ---637016289-605019937-1347780338=:70085 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Env: Windows/apa= che 2.2
 htt= pd.conf:   Forward proxy configuration with Basic auth.

Why would httpd respond with 403 for = a valid http request?
There are no special restrictions c= onfigured besides basic Proxy setup on top of standard httpd.conf (after cl= ean install).
---637016289-605019937-1347780338=:70085--