Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

udp high ports, d-link extract firmware dsl-2750u, wwwwxxxxx.2G, yxxxcom, WWWXXX, ftp://192.168.100.100, wwwxxx 100, www.xxxcon, wwwxxx, oom killer misbehaves postgresql

Links

XODOX
Impressum

#1: CacheEnable and mod_proxy

Posted on 2006-06-28 22:14:17 by Ryan Pendergast

------=_Part_20626_16167147.1151525657515
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I am trying to setup caching for my 2.2.2 Apache Proxy server. How do you
setup the server to cache all forward proxy requests?

By looking at the CacheEnable example in the documentation it seems as if I
would have to enable it for every protocol. Also the current documentation
is a bit misleading -
http://httpd.apache.org/docs/2.2/mod/mod_cache.html#cacheena ble states:

# Cache proxied url's
CacheEnable disk /

This however will not cache proxied urls will it? A proxy request does not
come in the form of 'Get /' - it comes in the form of 'GET http://'
(<protocol>://). I can see the above example caching requests to / and
below that are setup via ProxyPass but not forward proxy.

Can I do something like this:

CacheEnable disk ://

Will this cover every protocol that forward proxy handles? Thanks.

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

I am trying to setup caching for my 2.2.2 Apache Proxy server.&nbsp; How do you setup the server to cache all forward proxy requests?<br><br>By looking at the CacheEnable example in the documentation it seems as if I would have to enable it for every protocol.&nbsp; Also the current documentation is a bit misleading -
<a href="http://httpd.apache.org/docs/2.2/mod/mod_cache.html#cacheenable"> http://httpd.apache.org/docs/2.2/mod/mod_cache.html#cacheena ble</a> states:<br><br><code>
# Cache proxied url's<br>
CacheEnable disk /<br><br></code>This however will not cache proxied urls will it? A proxy request does not come in the form of 'Get /' - it comes in the form of 'GET http://' (&lt;protocol&gt;://).&nbsp; I can see the above example caching requests to / and below that are setup via ProxyPass but not forward proxy.
<br><br>Can I do something like this:<br><br>CacheEnable disk ://<br><br>Will this cover every protocol that forward proxy handles? Thanks.<br>

------=_Part_20626_16167147.1151525657515--

Report this message

#2: Re: CacheEnable and mod_proxy

Posted on 2006-07-01 13:47:10 by wrowe

Just to point out - modproxy-dev@a.o is closed some time ago.

Either dev@httpd.apache.org for development discussions, or
docs@httpd.apache.org for the documentation/manual author's list
or users@httpd.apache.org for user configuration issues are more
likely to attract the right attention depending on the post.

I'm curious - we should track down any remaining pointers at the
modproxy-dev list and ensure it's completely phased out.


Ryan Pendergast wrote:
> I am trying to setup caching for my 2.2.2 Apache Proxy server. How do
> you setup the server to cache all forward proxy requests?
>
> By looking at the CacheEnable example in the documentation it seems as
> if I would have to enable it for every protocol. Also the current
> documentation is a bit misleading -
> http://httpd.apache.org/docs/2.2/mod/mod_cache.html#cacheena ble states:
>
> | # Cache proxied url's
> CacheEnable disk /
>
> |This however will not cache proxied urls will it? A proxy request does
> not come in the form of 'Get /' - it comes in the form of 'GET http://'
> (<protocol>://). I can see the above example caching requests to / and
> below that are setup via ProxyPass but not forward proxy.
>
> Can I do something like this:
>
> CacheEnable disk ://
>
> Will this cover every protocol that forward proxy handles? Thanks.

Report this message

#3: Re: CacheEnable and mod_proxy

Posted on 2006-07-07 07:25:33 by wrowe

William A. Rowe, Jr. wrote:
> Just to point out - modproxy-dev@a.o is closed some time ago.
>
> Either dev@httpd.apache.org for development discussions, or
> docs@httpd.apache.org for the documentation/manual author's list
> or users@httpd.apache.org for user configuration issues are more
> likely to attract the right attention depending on the post.

Based on feedback, I've already modified the website for this list
to be archive only, and put an action item in to close it. Thanks
all who've participated, see you all on dev@httpd.a.o :)

Report this message