Bug 61107 - Feature Request: Don't ignore ServerAlias when using IP-based VirtualHost Matching
Summary: Feature Request: Don't ignore ServerAlias when using IP-based VirtualHost Mat...
Status: RESOLVED INVALID
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.4.10
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-19 12:31 UTC by info
Modified: 2017-05-19 12:37 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description info 2017-05-19 12:31:20 UTC
Hi,

the documentation states that ServerAlias only has an effect when the VirtualHost uses *:PORT and not IP:PORT.

This is highly irritating and confusing.
Weirdly enough, the ServerName directive is being used when finding the right virtual host even when its ip-based matching (at least using SSL).

So a user that wants 1 Domain + 1 Alias on IP A and another 1 Domain + 1 Alias in IP B must resort to using separate virtual host configurations in order to make it work. or he must use *:PORT which no longer enforces IP to Domain.

I think this is just an unnecessary behaviour.
why should *:443 match differently than IP:443 regarding the ServerAlias directives?

Or is it a coincidence that this works at all under SSL because of SNI and was never supposed to?

regards
Ludwig
Comment 1 info 2017-05-19 12:37:05 UTC
ok i had a bad configuration... sry the bug is bogus...