On 29-ago-09, at 18:32, Gunnar Wolf wrote: > Alvaro Lopez Ortega dijo [Sat, Aug 29, 2009 at 06:27:19PM +0200]: >>> So how do I fix this and why was the fix not made automatic ? >> >> Change whatever rule to set to use "Generic Balancer" to use "HTTP >> Reverse Proxy". >> >> It was not upgraded automatically because it's an important change >> you >> should aware of. The reverse proxy is much better than the deprecated >> 'Generic Balancer'. However, since it also allows to perform new >> operations, I encourage you to check its configuration and ensure >> that >> it's set up according to your needs. > > Can you please spell out a recipee on how this could be done?
From Cherokee-admin it'd only require to check the behavior rules and reconfigure all the rule using 'Generic Balancer' to 'HTTP Reverse Proxy' and check its configuration parameters. After that, save the configuration. > I understand you want to encourage users to be aware of features and > prefered habits, but distributions will try to make things transparent > - A user might not even care about which webserver he is running, he > should only care that it runs fine! Cherokee did not use the "Generic Balancer" module in the default configuration. If the module is in use, it's because the user added explicitly a rule. In my understanding, 'Generic Balancer' is a specialized enough module to let the user make the change by hand. I mean, I bet that someone who configured a generic TCP connection balancer in his web server will like to know about its deprecation and replacement module. Besides, the bast majority of the users will not realized of the change just because they don't use the module. I don't know what the best upgrading strategy for Debian is. I guess that if " = mirror$" were matched in the configuration file, the user would be warned at the end of the installation. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
