Solved

Virtual Hosts w/Apache 1.3, Solaris 2.5.1

Posted on 1998-07-01
4
255 Views
Last Modified: 2013-12-16
I am upgrading from Apache 1.1.1 to 1.3.0, and I ran into a problem with the <VirtualHost> configuration.  Previously, I had the following in httpd.conf:

        <VirtualHost 128.200.149.10>
        ServerAdmin cmfao@uci.edu
        DocumentRoot /...apache_1.1.1_dir/htdocs/med
        ServerName www.com.fao.uci.edu
        ErrorLog logs/com-error_log
        TransferLog logs/com-access_log
        </VirtualHost>

and everything worked fine.

Right now, I have not removed the old server yet (I want to test the new server before putting it into production).  So, I am running the 1.3 server on port 8000.  When I tried accessing the main server page (by going to www.fao.uci.edu:8000), it kept displaying the virtualhost page.  I noticed that NameVirtualHost seems to be required now, so I tried that, but that didn't help.  Below is the section from the new httpd.conf:

        NameVirtualHost 128.200.149.10:8000

        <VirtualHost 128.200.149.10:8000>
        ServerAdmin root@azalea.fao.uci.edu
        DocumentRoot /... apache_1.3.0_dir/htdocs/
        ServerName www.fao.uci.edu
        ErrorLog logs/error_log
        TransferLog logs/access_log
        </VirtualHost>
       
        <VirtualHost 128.200.149.10:8000>
        ServerAdmin cmfao@uci.edu
        DocumentRoot /... apache_1.3.0_dir/htdocs/med
        ServerName www.com.fao.uci.edu
        ErrorLog logs/com-error_log
        TransferLog logs/com-access_log
        </VirtualHost>

Any suggestions?
0
Comment
Question by:cokeman_
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 

Accepted Solution

by:
beacker earned 50 total points
ID: 1812273
You need to add the following Listen directive before the
applicable VirtualHost directive:

Listen 128.200.149.10:8000

<VirtualHost 128.200.149.10:8000>

Brad
0
 

Author Comment

by:cokeman_
ID: 1812274
When I put the server into production (ie, remove the references to port 8000 and let it run off of port 80), would I still need the Listen directive?
0
 

Expert Comment

by:beacker
ID: 1812275
You will either need to leave the Listen in place, or use the
Bind directive to let httpd know which addresses to work with.

0
 

Author Comment

by:cokeman_
ID: 1812276
muchas gracias
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In tuning file systems on the Solaris Operating System, changing some parameters of a file system usually destroys the data on it. For instance, changing the cache segment block size in the volume of a T3 requires that you delete the existing volu…
I promised to write further about my project, and here I am.  First, I needed to setup the Primary Server.  You can read how in this article: Setup FreeBSD Server with full HDD encryption (http://www.experts-exchange.com/OS/Unix/BSD/FreeBSD/A_3660-S…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
In a previous video, we went over how to export a DynamoDB table into Amazon S3.  In this video, we show how to load the export from S3 into a DynamoDB table.

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question