Ok, sorry, it seems that I misunderstood the problem.
I am also not qualified to answer your proxy questions per se.
My only remark would be : if you are already using Apache as a front-end
anyway, why don't you do the whole "Dav thing" at the Apache level,
instead of at the Tomcat level ? Wou
As you suggested, The file (I have omitted it before) is ok (tomcat baseed
basic auth)
The question/matter/problem was:
The app1 and the webdav app works only if:
httpd.conf
...
ok
ProxyPass /app1/ ajp://www.example.com:8009/app1/
ProxyPass / http://www.example.com:8080/
ProxyPassR
Hi.
Ah ! your Dav is at the Tomcat level, not the Apache level.
And that's also where the Dav authentication is being done.
In other words, no authentication and no Dav is being handled at the
Apache level, so it has nothing to do with the Apache proxying, which
probably works fine.
I believ
here is the conf:
Frontend server:
ServerName www.example.com
ProxyPass /favicon.ico !
ProxyPass /robots.txt !
ProxyPass /images/ !
ProxyPass /balancer !
ProxyPass /status !
ProxyPass /manager !
ProxyPass /host-manager !
Prox
Michele Mase' wrote:
I've the following problem:
A ftontend server with apache2.2.x (http1.1)
mod_proxy
mod_proxy_ajp
A backend server:
tomcat 6.x with 2 webapps:
/app1
/app2 (webdav, basic authentication via http)
Problem:
/app1 works well under proxy_ajp:
ProxyPass /some_path ajp://server:8
I've the following problem:
A ftontend server with apache2.2.x (http1.1)
mod_proxy
mod_proxy_ajp
A backend server:
tomcat 6.x with 2 webapps:
/app1
/app2 (webdav, basic authentication via http)
Problem:
/app1 works well under proxy_ajp:
ProxyPass /some_path ajp://server:8009/app1
webdav authen
