cp behind apache - mod_rewrite blues

That's great thanks very much.

It seems that it was the mod_proxy requirement that was
getting me. On
my installation mod_proxy is protected by a
"<IfDefine PROXY>" and so
it required a bit of -DPROXY to get it going but then it
worked.

There's lots of doco around being careful when using
mod_proxy. My
reading of it is that invoking mod_proxy but using a
"ProxyRequests
Off" directive is sufficient to (A) allow the standard
CP/Apache thing
to work but (B) disallow any other unwanted proxying
activity.

I'm going to look into this a bit more but I just thought I
would
mention it as presumably everyone trying to use CP/Apache
has to face
this issue.

thanks again for your help.

regards

richard.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---

On Sun, Feb 26, 2006 at 06:03:36PM -0800, northof40
wrote......

> There's lots of doco around being careful when using
mod_proxy. My
> reading of it is that invoking mod_proxy but using a
> "ProxyRequests Off" directive is sufficient
to (A) allow the
> standard CP/Apache thing to work but (B) disallow any
other
> unwanted proxying activity.

That has been my experience with Apache 1.3 as well.

Without mod_proxy, it just doesn't work.  But with it, and
ProxyRequests set to 'Off', cherrypy works just fine.

I've also tried various ways to connect to 3rd party sites
via my
server to test for an open proxy (using GET, CONNECT, HEAD)
and so
far it does not seem to be an open proxy.

Not sure what, if anything, is different if using Apache
2.0.

Kevin

-- 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---

"northof40" <shearichardgmail.com> writes:

> That's great thanks very much.
>
> It seems that it was the mod_proxy requirement that was
getting
> me. On my installation mod_proxy is protected by a
"<IfDefine
> PROXY>" and so it required a bit of -DPROXY to
get it going but then
> it worked.
>
> There's lots of doco around being careful when using
mod_proxy. My
> reading of it is that invoking mod_proxy but using a
"ProxyRequests
> Off" directive is sufficient to (A) allow the
standard CP/Apache
> thing to work but (B) disallow any other unwanted
proxying activity.

That's good to know.  I will add that to the updated recipe
that I am
working on for putting CherryPy behind Apache.

> I'm going to look into this a bit more but I just
thought I would
> mention it as presumably everyone trying to use
CP/Apache has to
> face this issue.

I would really appreciate it if you could forward anything
interesting
you might find to the list.  Apparently I don't know as
much about
Apache as I thought .

> thanks again for your help.
>
> regards
>
> richard.

Thank you,

Jason Earl

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---