Recently faced a situation where even after removing a VirtualHost, its ServerName was giving HTTP 200 response. It was all because of missed RTFM agenda.
When VirtualHosts get applied in Apache HTTPD server configuration, the first definition encountered by Apache Controller gets selected as the default route logic selected if the ServerName doesn't match any provided.
To get an explicit _default_ provider, one of the vhost definitions need to be told so... as in last configuration file piece.
When VirtualHosts get applied in Apache HTTPD server configuration, the first definition encountered by Apache Controller gets selected as the default route logic selected if the ServerName doesn't match any provided.
To get an explicit _default_ provider, one of the vhost definitions need to be told so... as in last configuration file piece.
No comments:
Post a Comment