I like the how-to a lot! Would it be useful to add a "logging" section explaining best practices about how to enable logging of the various modules? A lot of people ask for instruction about how to track what mod_proxy does in the background, plus I think it would be really useful to have a history of the status of each BalancerMember over time (for example to correlate when a backend server was put out of the Balancer set due to health check failures with access/error/etc.. logs after an outage - a balancer-manager history written down somewhere).
Hope that this make sense! Luca 2016-02-12 10:04 GMT+01:00 Daniel <[email protected]>: > Looks very nice indeed! For being a "rough" version looks quite complete. > Also the diagram is a cool addition to help people understand how reverse > proxying works. > > I think the examples may need some adjusting with the matching slashes: > > ProxyPass "/" "http://www.example.com"; > should be: > ProxyPass / http://www.example.com/ > (I removed the quotes because they are not necessary) > > and > ProxyPass "/images" "http://www.example.com"; > should be: > ProxyPass /images/ http://www.example.com/ > > > Cheers! > > > > > El vie., 12 feb. 2016 a las 9:48, Stefan Eissing (< > [email protected]>) escribió: > >> Very nice! >> >> > Am 11.02.2016 um 18:46 schrieb Jim Jagielski <[email protected]>: >> > >> > A rough and very brief framework of such a guide is now available... >> > >> > http://httpd.apache.org/docs/trunk/howto/reverse_proxy.html >> > >> > On 2016-02-10 06:21, Luca Toscano <[email protected]> wrote: >> >> 2016-02-10 10:33 GMT+01:00 Stefan Eissing < >> [email protected]>: >> >> >> >>> If you write one, I write one for http2! :-) >> >>> >> >>> >> >> +1+1+1+1 :) >> >> >> > ------ >> > Sent via Pony Mail for [email protected]. >> > View this email online at: >> > https://pony-poc.apache.org/[email protected] >> >>
