As part of the setup for NameVirtualHost delivery of my websites I forgot to add a VirtualHost directive for the initial page shown when you simply enter http://serverip:80/. This causes the apache server to return the information found in the initial VirtualHost container we had defined. This was pointing to our new Software Packaging Manager instance so we got the sign on page even though we went through a different port initially. To fix this we had to add another VirtualHost container as below to the config in /usr/local/Zend/Apache2/conf/httpd.conf file.
# Zendcore default server
DirectoryIndex index.php index.html DocumentRoot /www/zendcore/htdocs ServerName www.zendcorre.local Options Indexes FollowSymLinks Order Deny,Allow Allow From All
We had left the original default server configurations as these should be picked up as the default, however further investigation through the Apache2 docs showed us the error of our ways.
This is a quote from the docs
Main host goes away
If you are adding virtual hosts to an existing web server, you must also create a
block for the existing host. The ServerName and DocumentRoot included in this virtual host should be the same as the global ServerName and DocumentRoot. List this virtual host first in the configuration file so that it will act as the default host.
So we added the VirtualHost container, stopped and started the apache instances through the ZCMENU options and the following screen is now correct presented to the user.
You are not required to add a virtualhost entry into our new webserver config (/www/phpserver/conf.httpd.conf) file as the original server (ZENDCORE) will be running to serve the request. It does not pass in the servername so the fact that we have put this entry in first causes the Apache PASE server to use this config when no others match by server name. This may need to be tidied up once you create more production ready environments. If you want to really tidy things up you should add a VirtualHost container to the ZENDCORE config in /www/zendcore/conf/httpd.conf, the problem with this approach is a Zend update may overwrite the config file?