>Number: 5406 >Category: config >Synopsis: The order of ServerAlias directives in Virtualhost directives >shouldn't matter. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Wed Dec 1 11:10:01 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.9 >Environment: n/a >Description: In the following config it is not possible to access the 'test.bla.com' site. If the <virtualhost> statements were switched, it would use the 'ServerAlias *' as a catch.
<virtualhost 1.1.1.1> Servername www.bla.com ServerAlias *.bla.com> </virtualhost> <virtualhost 1.1.1.1> Servername test.bla.com </virtualhost> >How-To-Repeat: >Fix: I think the most logical fix is to make 'ServerAlias *' act as a catch. IE, the order of ServerAlias statements shouldn't matter anymore. This is the behaviour of several other unix config files like the 'virtusertable' file. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
