Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of pikodemo@gmail.com designates
 209.85.198.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=Mrt4hcQ8R/hi+1zaA6MvzktHcBGfbGsMkN0Vl9d97/Pk3+XDds4/050lwh/VWA6C7byCxm1AYO9UTCRPY66rUxtxmQGLAKXec99CYSjk/GBV1E8tdfCj2Q9odObdy2+JberRbpUrPj4yCi3dUS690Ich9KW9rmbQ3qW1f+pdehs=
Message-ID: <36f1b6710710290447v4bf2162eydefcf509f84a39bc@mail.gmail.com>
Date: Mon, 29 Oct 2007 11:47:09 +0000
From: "Laurent Tu" <pikodemo@gmail.com>
To: users@httpd.apache.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_14649_17830449.1193658429686"
Subject: [users@httpd] Proxy authentication bypassed when serving cached
 content?

------=_Part_14649_17830449.1193658429686
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,


When using user authentication along with cache, I saw that user
authentication was not asked again when the content was served from the
cache.
I am using authentication inside a proxy directive:
<Proxy *>
  AuthType Basic
  ...
</Proxy>

When the content is not cached yet, Proxy-Authenticate  is sent by the proxy
server. When the content is already cached, it provides the result even
without the client providing Proxy-Authorization header.
For example, this happens with a website like http://www.perdu.com


After going through mod_cache doc, mod_proxy doc or rfc 2616, I've found
nothing about it. Can anyone please tell me if I'm understanding something
the wrong way?


Thanks
Laurent

------=_Part_14649_17830449.1193658429686
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,<br><br><br>When using user authentication along with cache, I saw that user authentication was not asked again when the content was served from the cache.<br>I am using authentication inside a proxy directive:<br>&lt;Proxy *&gt;
<br>&nbsp; AuthType Basic<br>&nbsp; ...<br>&lt;/Proxy&gt;<br><br>When the content is not cached yet, Proxy-Authenticate&nbsp; is sent by the proxy server. When the content is already cached, it provides the result even without the client providing Proxy-Authorization header.
<br>For example, this happens with a website like <a href="http://www.perdu.com">http://www.perdu.com</a><br><br><br>After going through mod_cache doc, mod_proxy doc or rfc 2616, I&#39;ve found nothing about it. Can anyone please tell me if I&#39;m understanding something the wrong way?
<br><br><br><br>Thanks<br>Laurent<br>

------=_Part_14649_17830449.1193658429686--