|Summary:||New issue appeared after update, ServerName directive was not set|
|Product:||Apache httpd-2||Reporter:||Hossein <hosseamin>|
|Component:||Core||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description Hossein 2019-03-15 22:59:39 UTC
I was able to figure out a problem in my site which was using virtualhost. I had my main domain in a virtualhost and `ServerName` attribute at root was commented out. After update my main domain did not link to the same RootDocument as before. After some trouble-shooting I thought the update may messed with the rules. Probably a new feature is active in v2.4.6 that looks for domain name associated with the running server and uses it as `ServerName`. If I'm right. Then this issue may result issues for others too. For those who have the same problem as me. Simply add ServerName at root with ipv4 address and port 80. To avoid auto-detection.