On Mon, Jan 9, 2017 at 10:14 PM, Yann Ylavic <[email protected]> wrote: > > I guess we have to do something for the latter, because we can't > change some file (like the $prefix's httpd.conf with the "legacy" > method) to avoid it, right?
Usually a simple "ServerName localhost" in the main server is enough for me to resolve the warnings, so couldn't we set/force it the generated check/conf/httpd.conf?
