Thomas Murgan writes: > This does not work for me: > ProxyPass /mailman http://internal-server/mailman > ProxyPassReverse /mailman http://internal-server/mailman
If you want all URLs starting with "http://external-server/mailman"; to be forwarded to corresponding URLs at "http://internal-server/mailman";, this is the correct syntax. If in fact what you want is something different, be specific. Without seeing the rest of the URL space configuration it's hard to guess what might be wrong. What do you mean by "doesn't work"? What errors are produced in the browser? What is in Apache's log? Check Apache's error log as well. Given that > http://external-server/listinfo >> http://internal-server/mailman/listinfo "works" (I assume you mean that produces the listinfo page from the Mailman installed on internal-server), I would guess that you have some configuration on external-server that interferes with configuring /mailman with ProxyPass. Was Mailman ever installed on external-server, so that there is an Alias or ScriptAlias for the path /Mailman on that Apache? Perhaps you have a Location or Directory element blocking the ProxyPass. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
