>Number: 1262 >Category: general >Synopsis: Vhost overlap reports indistinguishable and to stderr only >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sun Oct 19 15:10:01 PDT 1997 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3b2 >Environment: N/A >Description: The new virtual-host log messages about <VirtualHost> overlaps are great and a wonderful debugging tool, but there are two problems with it:
1. They get reported so early in the config parsing that they come out on stderr - so they never appear in the ErrorLog for later reference. Having to restart the server to reproduce them is not a very good option. 2. If there are problems with my name-vhosts, and they're defined using <VirtualHost n.n.n.n>, the messages complain strictly about the n.n.n.n identity. If all my <VirtualHost> containers use that syntax, there's no way to tell which ones are having problems. The log message should include the value from ServerName directive inside the <VirtualHost> container, or some other way of identifying which ones have problems. You're welcome for my using Apache. <g> >How-To-Repeat: IOTTMCO >Fix: >Audit-Trail: >Unformatted:
