On Friday, Sep 24, 2004, at 16:59 Europe/London, Martijn Koster wrote:
I've not needed to setup a reverse proxy, but the mod_proxy documentation page says you need a:
ProxyRequests Off <Proxy *> Order deny,allow Allow from all
</Proxy> ProxyPass /foo http://foo.example.com/bar ProxyPassReverse /foo http://foo.example.com/bar
Do you have an Allow like that?
I do now!
Thanks very much, its all working now.
On Friday, Sep 24, 2004, at 17:02 Europe/London, Andrew Savory wrote:
On 24 Sep 2004, at 16:42, Richard Lewis wrote:
I've got two Cocoon (2.1) webapps running under Tomcat (4.1) on my server (Debian, j2sdk1.4-sun, Apache 2.0). My network service provided has given me two aliases for the machine which I want to point to the two webapps.
For shame, Richard, for shame. This is not the cocoon-users mailing list, you know ;-)
I tried them but no one answered :-(
Anyway ALUG people are much more often correct about things than anywhere else ;-)
Dump Tomcat, run both sites through Jetty (you really -don't- want to run two Cocoon instances, look at mount-table.xml for the quickest way to mangle your Cocoon urlspace safely. Follow the wiki docs, they are very good.
(Actually, its just one Cocoon instance). Is Jetty really better, I thought the documentation said that Jetty was provided for a test environment rather than production?
Thanks for your help, Richard
Hi,
On 25 Sep 2004, at 15:57, Richard Lewis wrote:
For shame, Richard, for shame. This is not the cocoon-users mailing list, you know ;-)
I tried them but no one answered :-(
Hrmph. People must be sleeping over there ;-)
Anyway ALUG people are much more often correct about things than anywhere else ;-)
Not sure I'd agree - people usually have a lot to say, but it's rarely well-balanced or totally accurate!
Dump Tomcat, run both sites through Jetty (you really -don't- want to run two Cocoon instances, look at mount-table.xml for the quickest way to mangle your Cocoon urlspace safely. Follow the wiki docs, they are very good.
(Actually, its just one Cocoon instance). Is Jetty really better, I thought the documentation said that Jetty was provided for a test environment rather than production?
Jetty is provided so that you can test without having to install a servlet container 'properly', but it is also a more-than-adequate production container. It has the advantage of being relatively lightweight, and has none of the nasty connector stuff which can be such a PITA with Tomcat.
A.