Virtual Hosts vs Localhost

OK, I'm on about step #13 of Apple's virtual hosts enabling obstacle course, and I'm still confused. I've modified the httpd.conf, hosts and NetInfo files, and I can now preview the home page of ONE of my virtual host sites. The problem is that I see the page whether I type in http://localhost/, http://Geobop/, http://GW/ or http://GS/. It should preview only at http://Geobop/.
I rediscovered the article Enabling Virtual Hosts on MacOS X at http://www.evolt.org/article/EnablingVirtual_Hosts_on_MacOSX/18/13138/
and added a script to my httpd.conf file, as follows:
# Leave this one alone - it makes sure that localhost works.
<VirtualHost 127.0.0.1>
DocumentRoot /Library/WebServer/Documents
ServerName localhost
</VirtualHost>
#<VirtualHost 127.0.0.1:80>
# ServerName geobop
# ServerAdmin [email protected]
# DocumentRoot /Users/MYNAME/Sites/Geobop
#</VirtualHost>
If I understand correctly, this is supposed to make http://localhost/ display something unique, rather than a local website. However, all the URL's I cited above still display the same thing...but this time around they display blank pages with columns of numerals along the left margin.
In an earlier experiment, I deleted all my virtual hosts from httpd.conf. Then all these URL's displayed the following:
Index of /
Name Last modified Size Description
[DIR] Parent Directory 13-Mar-2007 15:49 -
[ ] index.php 06-Oct-2006 15:36 1k
[ ] php5.fcgi 06-Oct-2006 18:18 1k
[ ] phpMyAdmin-2.9.0.2.tar 06-Oct-2006 17:44 11.4M
[ ] phpinfo.php 06-Oct-2006 15:20 1k
[ ] phpinfo.php5 06-Oct-2006 18:20 1k
Apache/1.3.33 Server at localhost Port 80
Can someone tell me what's going on and how to fix it. This process was three times easier on my PC, though I hate Microsoft.
Thanks.

Thanks for your explainations but it keeps frustrating me. I'll try to give an exact overview to my settings and my tries to implement your suggestions:
Computer name: MacBook Pro
Host: server.local
Wi-Fi: 192.168.178.100 (static, as I said no DHCP)
DNS-Settings:
Forwarding Servers: 192.168.178.100
Perform lookups for only some clients: "The server itself" and "Clients on the local network"
Host name: server.local
IP address: 192.168.178.100
(no aliases)
automatically created after setting this host name:
     Primary zone: server.local
     Machine: zone: server.local, host name: server.local, IP address: 192.168.178.100
     Nameserver: zone: server.local, Name-server: server.local
Now I create a new host:
Host name: thenewwebsite.site
IP address: 192.168.178.100
(no aliases)
automatically created after setting this host name:
     Primary zone: thenewwebsite.site
     Machine: zone: thenewwebsite.site, host name: thenewwebsite.site, IP address: 192.168.178.100
     Nameserver: zone: thenewwebsite.site, Name-server: thenewwebsite.site
Now going to "Web" service:
hit the [+] button
domain-name: thenewwebsite.site
--> and it gives me the red bullet again saying it could not resolve this and trying to load "thenewwebsite.site" from the browser consequently fails.
I also tried to set the machine-zone and the nameserver-zone for the thenewwebsite.site host to server.local - didn't changed anything, loading "thenewwebsite.site" fails.
Designed in California, designed to make ist easier ??? huu ???

Similar Messages

Should I be able to access virtual host via localhost/site path?

I finally have been able to successfully set up a virtual host on my local host.
I can access http://localhost which redirects me to the http://localhost/xampp page and I can access my local site with http://nif.local/. I thought I had read that I should still be able to access my local nif site via http://localhost/nif.local. Is that correct? If so, what should I check since I get a 404 error via the second way? I just want to make sure everything is set up correctly.
Thank you.

Now sorted;-). Can disable Siri in settings for when phone is locked. Why is this not default?

Creating multiple virtual hosts on localhost failed

For developing a website I want to setup some virtual hosts on the localhost of the OS X Server.
Trying to setup them up via "Services -> Websites -> [+]" failed because the domain name won't be resolved.
I creates a virtual host called "thewebsite.site" some time ago - this virtual host works well although the bullet next
to the "thewebsite.site" within the domain name imput fields actually shows red (for my complete irritation it sometimes
the bullet turns to green for a while - I don't know why and when because I changed nothing)

Thanks for your explainations but it keeps frustrating me. I'll try to give an exact overview to my settings and my tries to implement your suggestions:
Computer name: MacBook Pro
Host: server.local
Wi-Fi: 192.168.178.100 (static, as I said no DHCP)
DNS-Settings:
Forwarding Servers: 192.168.178.100
Perform lookups for only some clients: "The server itself" and "Clients on the local network"
Host name: server.local
IP address: 192.168.178.100
(no aliases)
automatically created after setting this host name:
     Primary zone: server.local
     Machine: zone: server.local, host name: server.local, IP address: 192.168.178.100
     Nameserver: zone: server.local, Name-server: server.local
Now I create a new host:
Host name: thenewwebsite.site
IP address: 192.168.178.100
(no aliases)
automatically created after setting this host name:
     Primary zone: thenewwebsite.site
     Machine: zone: thenewwebsite.site, host name: thenewwebsite.site, IP address: 192.168.178.100
     Nameserver: zone: thenewwebsite.site, Name-server: thenewwebsite.site
Now going to "Web" service:
hit the [+] button
domain-name: thenewwebsite.site
--> and it gives me the red bullet again saying it could not resolve this and trying to load "thenewwebsite.site" from the browser consequently fails.
I also tried to set the machine-zone and the nameserver-zone for the thenewwebsite.site host to server.local - didn't changed anything, loading "thenewwebsite.site" fails.
Designed in California, designed to make ist easier ??? huu ???

A second virtual host is deaf

Apache 2 and Tomcat 4.0 work together here on an NT as long as httpd.conf sees the Tomcat contexts denoted as a virtual host with the same name as the host : "host1".
So, I am trying now to use a second virtual host "host2" on my machine "host1".
I can still reach the contexts on host1 with http://host1/things
but should this also work? : http://host2/otherthings
must I give my system 2 (two) ip addresses in order to have a second virtual host? Seems strange.

yes and the link you posted before does actually mention this fairly important issue
Of course, you can't just make up names and place them in ServerName or ServerAlias. You must first have your DNS server properly configured to map those names to an IP address associated with your server.i suspect that is you want to test on win network if you don't want to mess about with dns you might be able to do some bejiggery in the LMHOSTS file that would have the same effect.
if you want to just test virtual hosts in general. one thing that also might work is using machine name(s) as well as the ip's
for example if the machine is called host1 and has an address of 192.168.100.10 then i think you could set up three sites.
the "real" (default) site.
192.168.100.10
127.0.0.1
virtual host 1
host1
virtual host 2
localhost
i think these would work although the last one would only work from the server itself. see virtual hosting uses the host header passed in HTTP so as long as you can have different ones that end up going to the same place you can invent some virtual hosts for testing.

Virtual Host (localhost) + Wamp 2.1

Hello
I'm trying to test a local URL like xxxxx.localhost or loclahost / xxxxxxx
This does not work.
I read this post related to this topic:
http://blogs.adobe.com/edgeinspect/2012/06/19/shadow-xip-io-virtual-hosts-workflow-simplif ied/
But I do not know what to do.
Thank you for your help.

No change.
Changes in the file are in bold and italics.
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/Program Files/Apache Software Foundation/Apache2.2" will be interpreted by the
# server as "C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log".
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default. It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
ServerRoot "c:/wamp/bin/apache/apache2.2.17"
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#Listen 12.34.56.78:80
#Listen 80
Listen 0.0.0.0:80
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule php5_module "c:/wamp/bin/php/php5.3.5/php5apache2_2.dll"
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User daemon
Group daemon
</IfModule>
</IfModule>
# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin admin@localhost
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
ServerName localhost:80
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "c:/wamp/www/"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "c:/wamp/www/">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    AllowOverride all
    # Controls who can get stuff from this server.
#   onlineoffline tag - don't remove
    Order Deny,Allow
#   Deny from all
    Allow from all
</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
    DirectoryIndex index.php index.php3 index.html index.htm
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "c:/wamp/logs/apache_error.log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel debug
<IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "c:/wamp/logs/access.log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "logs/access.log" combined
</IfModule>
<IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://localhost/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "cgi-bin/"
</IfModule>
<IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock logs/cgisock
</IfModule>
# "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
<IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    AddType application/x-httpd-php .php
    AddType application/x-httpd-php .php3
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://localhost/subscription_info.html
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#EnableMMAP off
#EnableSendfile off
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf
# Language settings
#Include conf/extra/httpd-languages.conf
# User home directories
#Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts (STE)
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
#Include conf/extra/httpd-default.conf
# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
#NameVirtualHost 127.0.0.1
#<VirtualHost 127.0.0.1>
#        ServerName localhost
#        DocumentRoot "C:\wamp\www"
#</VirtualHost>
NameVirtualHost 192.168.1.98
<VirtualHost 192.168.1.98>
        ServerName 192.168.1.98
        DocumentRoot "C:\wamp\www"
</VirtualHost>
Include "c:/wamp/alias/*"

Does Apache Virtual Hosting work with localhost?

I'm a newbie trying to learn how apache web server works. I've activated apache web server on my Mac PowerBook G4, and tweaked the config file to get PHP, SSI and CGI working.
If I type the url http://127.0.0.1/ I get the same page as http://localhost/
If localhost is the domain name for the address 127.0.0.1, can I assign other domain names to 127.0.0.1 using apache's virtual hosting?
Ti Powerbook G4 Mac OS X (10.4.4)

localhost is defined as 127.0.0.1. You can use them interchangeably.
As for virtual hosts, sure. Apache doesn't care.
There are two ways of running virtual hosts.
Port-based virtual hosts use a port number other than the standard 80. They can be accessed via something like http://localhost:8000/
Name-based virtual hosts look at the hostname header in the request to work out which site to serve. You can run any number of sites on the same port number this way, but you need to be able to control DNS so that it points to your machine.
If you are just testing this locally you can edit /etc/hosts to add whatever hostnames you like;
127.0.0.1 localhost my.testsite.com me.mydomain.com
Now when you enter 'my.testsite.com' or 'my.mydomain.com' in your web browser, /etc/hosts will resolve this to 127.0.0.1 and you'll talk to your local apache server.
Note that the localhost entries don't have to be in your domain. You can use this to override any real hostname you like.
Of course, if you want remote users to access this site you'll need to setup something in the DNS, or edit their /etc/hosts files individually.

Viewing ColdFusion 9 Mac localhost sites that are rerouted via virtual host on VMWare Fusion PC

Hey, I've got some localhost CF9 stuff running on my mac that are rerouted via virtual host and etc/host file to be like local.myprojectname.dev and I'm trying to set things up in VMWare Fusion PC so I can view in a browser. I've gotten as far as being able to add an IP to the PCs host file, and then pull up the root directory of the localhost but can't seem to figure out how to get the virtual host domain to work. This make any sense?

You will need to configure Host header support in your web server software. Both IIS and Apache support Host headers, but they're configured differently of course.
Then, if you want those Host headers to route on your Mac host OS, you'll need to map them in /etc/hosts to your VM's IP address.
Dave Watts, CTO, Fig Leaf Software

Localhost/Virtual Host Blues

I'm totally confused. I hired someone to help me set up Apache, PHP, MySQL, phpMyAdmin and virtual hosts on my MacBook Pro, but he and I both made some mistakes, and the results are a mess.
Obviously, I need to go back to square one, and I think that means fixing "localhost," but I'm not sure how to do it. Anyway, I thought if I listed everything I've done so far, someone might spot the problem...
First, I've placed all my websites and phpMyAdmin inside /Users/davidblomstrom/Sites
I found phpMyAdmin's config.inc.php file and edited the $cfg line to this:
$cfg['PmaAbsoluteUri'] = 'http://Users/davidblomstrom/Sites/phpMyAdmin/';
I logged two websites (Geobop and GW) and phpMyAdmin into NetInfo and created the following virtual hosts in httpd.conf:
<VirtualHost 127.0.0.1:80>
ServerName geobop
ServerAdmin [email protected]
DocumentRoot /Users/davidblomstrom/Sites/Geobop
</VirtualHost>
<VirtualHost 127.0.0.1:80>
ServerName phpMyAdmin
ServerAdmin [email protected]
DocumentRoot /Users/davidblomstrom/Sites/phpMyAdmin
</VirtualHost>
<VirtualHost 127.0.0.1:80>
ServerName gw
ServerAlias gw *.gw
DocumentRoot /Users/davidblomstrom/Sites/GW
</VirtualHost>
At least one of my virtual hosts was working, as it displayed my website Geobop. Unfortunately, I had put that website in the wrong location. Now that it's in the right location, it doesn't work.
When I type in http://localhost, it asks me for a username and password, but it won't accept anything I type in.
When I type in http://Geobop, it says "Looking up users," then displays phpMyAdmin's home page (minus images). When I try to display a database, it defaults to some online website.
When I type in http://GW (my second website I've created a virtual host for), I'm prompted for a User Name and Password, with this message: "Enter username and password for 'phpMyAdmin running on localhost' at http://gw."
So, again, it appears to me that I need to go back to square one and make http://localhost display whatever it's supposed to display. I also appears that phpMyAdmin has somehow become confused with my websites.
Ironically, this is probably the first issue I've discovered that was actually easier to deal with on my PC.
Thanks.

I'm totally confused. I hired someone to help me set up Apache, PHP, MySQL, phpMyAdmin and virtual hosts on my MacBook Pro, but he and I both made some mistakes, and the results are a mess.
Obviously, I need to go back to square one, and I think that means fixing "localhost," but I'm not sure how to do it. Anyway, I thought if I listed everything I've done so far, someone might spot the problem...
First, I've placed all my websites and phpMyAdmin inside /Users/davidblomstrom/Sites
I found phpMyAdmin's config.inc.php file and edited the $cfg line to this:
$cfg['PmaAbsoluteUri'] = 'http://Users/davidblomstrom/Sites/phpMyAdmin/';
I logged two websites (Geobop and GW) and phpMyAdmin into NetInfo and created the following virtual hosts in httpd.conf:
<VirtualHost 127.0.0.1:80>
ServerName geobop
ServerAdmin [email protected]
DocumentRoot /Users/davidblomstrom/Sites/Geobop
</VirtualHost>
<VirtualHost 127.0.0.1:80>
ServerName phpMyAdmin
ServerAdmin [email protected]
DocumentRoot /Users/davidblomstrom/Sites/phpMyAdmin
</VirtualHost>
<VirtualHost 127.0.0.1:80>
ServerName gw
ServerAlias gw *.gw
DocumentRoot /Users/davidblomstrom/Sites/GW
</VirtualHost>
At least one of my virtual hosts was working, as it displayed my website Geobop. Unfortunately, I had put that website in the wrong location. Now that it's in the right location, it doesn't work.
When I type in http://localhost, it asks me for a username and password, but it won't accept anything I type in.
When I type in http://Geobop, it says "Looking up users," then displays phpMyAdmin's home page (minus images). When I try to display a database, it defaults to some online website.
When I type in http://GW (my second website I've created a virtual host for), I'm prompted for a User Name and Password, with this message: "Enter username and password for 'phpMyAdmin running on localhost' at http://gw."
So, again, it appears to me that I need to go back to square one and make http://localhost display whatever it's supposed to display. I also appears that phpMyAdmin has somehow become confused with my websites.
Ironically, this is probably the first issue I've discovered that was actually easier to deal with on my PC.
Thanks.

[SOLVED] XAMPP 1.8.0 + virtual hosts = 403 access forbidden

Hello, all. I am happy migrant from ubuntu to arch, but have problem, which i can't solve myself.
I need to setup xammp for local development.
My actions
Install last xampp from aur
Run lampp
Open locahost, there is "xampp welcome page"
Open localhost/phpmyadmin and get
xampp new xampp security concept, blablabla
Okay, add "Require all granted" in httpd-xampp.conf
<Directory "/opt/lampp/phpmyadmin">
   AllowOverride AuthConfig Limit
   #Order allow,deny
   #Allow from all
   Require all granted
</Directory>
phpmyadmin came back
I need virtual hosts, structure will be
/home/$USER/Sites/{site1/index.html,site2,site3 etc.}
Uncomment include vhosts in httpd.conf
Include /Applications/XAMPP/etc/extra/httpd-vhosts.conf
Clear httpd-vhosts.conf and put there
<VirtualHost *:80>
   DocumentRoot "/home/shara/Sites/mysite"
   ServerName mysite
   ServerAlias www.mysite
   ErrorLog "/home/shara/Sites/mysite-error_log"
   CustomLog "/home/shara/Sites/mysite-access_log" common
</VirtualHost>
Add new host in /etc/hosts
127.0.0.1 mysite
Set "User shara" and "Group www" in httpd.conf
<IfModule unixd_module>
User shara
# commented out by lampp compatibility check
#Group nogroup
Group www
</IfModule>
Add group "groupadd www"
Add user to group "usermod -aG www shara"
Change htdocs group "chgrp -R www /opt/lampp/htdocs"
Change sitedir group "chgrp -R www /home/shara/Sites"
Change htdocs chmod "chmod 2775 /opt/lampp/htdocs"
Change sitedir chmod "chmod 2775 /home/shara/Sites"
Run xampp
Open "mysite"
Access forbidden Error 403
Open "localhost"
Access forbidden Error 403
Open "localhost/phpmyadmin"
Existing configuration file (./config.inc.php) is not readable.
Oookay
Set chmod 664 to /opt/lampp/phpmyadmin/config.inc.php
Open "localhost/phpmyadmin"
phpmyadmin works, but nothing else
XAMPP 1.7 worked perfect with this config. Where is the FAIL?
Last edited by Shara (2012-09-04 12:18:48)

I did it.
phpmyadmin new security problem solved with set passwords with /opt/lampp/lampp security (NO require all granted in httpd-xampp.conf)
virtual hosts 403 problem solved with
New instruction:
*User name "shara" and group "www" is myown, you need to set yours
INSTALL
yaourt -S xampp
/opt/lampp/lampp security
VIRTUAL HOSTS
Uncomment including vhosts in "/opt/lampp/etc/httpd.conf" and set "User shara" and "Group www"
Include /Applications/XAMPP/etc/extra/httpd-vhosts.conf
<IfModule unixd_module>
User shara
# commented out by lampp compatibility check
#Group nogroup
Group www
</IfModule>
Clear "/opt/lampp/etc/extra/httpd-vhosts.conf" and add
<VirtualHost *:80>
DocumentRoot "/home/shara/Sites/mysite"
ServerName mysite
ErrorLog "/home/shara/Sites/mysite/mysite-error.log"
CustomLog "/home/shara/Sites/mysite/mysite-access.log" common
<Directory "/home/shara/Sites/mysite">
Require all granted
</Directory>
</VirtualHost>
Add new host in /etc/hosts
127.0.0.1 mysite
Add group
groupadd www
Add user to group
usermod -aG www shara
Change htdocs group
chgrp -R www /opt/lampp/htdocs
Change sitedir group
chgrp -R www /home/shara/Sites
Change htdocs chmod
chmod 2775 /opt/lampp/htdocs
Change sitedir chmod
chmod 2775 /home/shara/Sites
Set phpmyadmin config chmod
chmod 664 /opt/lampp/phpmyadmin/config.inc.php
Run lampp
sudo /opt/lampp/lampp start
WIN ^_^
May i need to write archwiki manual?
Last edited by Shara (2013-02-28 17:07:22)

The essential guide to DW cs4... by D. Powers: when from wamp to xampp+virtual host and having problems :(

Following the book in chapter 2 I think Ivé followed everything correctly, but have encluded all the things I've edited below.
I was using wamp with no problems but after trying to set up a virtual host and now using xampp im abit lost its probabsomething stupid but I can find the prob.
(This post is abit long and dragged out so I used some colour to try ease the reading..)
When I try to view a dynamic page in live view or in firefox I get the following error:
**when using:
<VirtualHost *:80>
DocumentRoot c:/xampp/htdocs
ServerName localhost
</VirtualHost>
result:
Access forbidden!
You don't have permission to access the requested object.     It is either read-protected or not readable by the server.
If you think this is a server error, please contact the webmaster.
Error 403
thegoodlife
2009/10/13 12:47:48 PM
Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0
*when using:
<VirtualHost *:80>
DocumentRoot c:/htdocs
ServerName localhost
</VirtualHost>
result:
Object not found!
The requested URL was not found on this server.          If you entered the URL manually please check your     spelling and try again.
If you think this is a server error, please contact the webmaster.
Error 404
thegoodlife
2009/10/13 12:32:58 PM
Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0
This is what I've done, blue indicating where I have or was meant to edit, red being the relivant context. (hope it helps )
1. Created a new folder called htdocs (C:\htdocs)
2. Changed the pathname to:
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "C:/htdocs"
and
# This should be changed to whatever you set DocumentRoot to.
<Directory "C:/htdocs">
3. Created vhosts folder; with a sub-folder called thegoodlife (C:\vhosts)
4. entered new vhost:
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
127.0.0.1 localhost
127.0.0.1 dwcs4
127.0.0.1 thegoodlife
127.0.0.1 bin.errorprotector.com ## added by CiD
5.It says uncomment the command by removing the #, (Supplemental configuation.), but this is the origional file; already uncommented?
# Real-time info on requests and configuration
Include "conf/extra/httpd-info.conf"
# Virtual hosts
Include "conf/extra/httpd-vhosts.conf"
# Distributed authoring and versioning (WebDAV)
Include "conf/extra/httpd-dav.conf"
6.Set the permissions and changed the code as instructed, unsing (c:/xampp/htdocs) as advised.
# You may use the command line option '-S' to verify your virtual host
# configuration.
<Directory C:/vhosts>
Order Deny,Allow
Allow from all
</Directory>
# Use name-based virtual hosting.
##NameVirtualHost *:80
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
<VirtualHost *:80>
DocumentRoot c:/xampp/htdocs
ServerName localhost
</VirtualHost>
<VirtualHost *:80>
DocumentRoot c:/vhosts/dwcs4
ServerName dwcs4
</VirtualHost>
<VirtualHost *:80>
DocumentRoot c:/vhosts/thegoodlife
ServerName thegoodlife
</VirtualHost>
Then creating the site definition:
local root forlder: C:\htdocs\thegoodlife\
testing server folder: C:\vhosts\thegoodlife\
URL prefix: http://thegoodlife/
hope i've covered all area's where I could have gone wrong

Just one more thing - the description of what i did while first Kernel appeared:
Happened 2 days ago. Wasn't turning it off for like a day, only sleep mode by closing it. Worked fine all day, wasn't doing anything, except for checking mail 2-3 times and having windows 7 virtual machine opened but doing nothing, everything was going fine. Then closed it without turning off.
Opened 3-4 hours later, everything was working fine for 30 minutes of checking mail, then Kernel appeared. After that pretty much everything i did is described in part 1-5.
Note: all the time MBP was connected to internet via wifi, so updates to both MBP and virtual machine of all programs were possible.
I only shared downloads and desktop folders, so windows couldn't have access to system folder of Mac Os.
Hope this might help...Thanks again.

How to set up Virtual Hosts in Apache (OS X Server 10.9)

I want to host more than one website on my mac mini with OS X Server 10.9
1.) I edited /etc/apache2/httpd.conf for uncommenting the include line:
# Virtual hosts
Include /private/etc/apache2/extra/httpd-vhosts.conf
2.) I edited /etc/apache2/extra/httpd-vhosts.conf and added:
<VirtualHost *:80>
    ServerName cammino-al-dente.net
    ServerAlias www.cammino-al-dente.net
    DocumentRoot "/Library/Server/Web/Data/Sites/cammino-al-dente.net"
    ErrorLog "/private/var/log/apache2/cammino-al-dente.net.com-error_log"
    CustomLog "/private/var/log/apache2/cammino-al-dente.net-access_log" common
    ServerAdmin [email protected]
</VirtualHost>
<VirtualHost *:80>
    ServerName sutterer.net
    ServerAlias www.sutterer.net
    DocumentRoot "/Library/Server/Web/Data/Sites/sutterer.net"
    ErrorLog "/private/var/log/apache2/sutterer.net-error_log"
    CustomLog "/private/var/log/apache2/sutterer.net-access_log" common
    ServerAdmin [email protected]
</VirtualHost>
3.) then I edited /etc/hosts/ to spoof my IP address to the domains:
127.0.0.1
localhost
127.0.0.1
cammino-al-dente.net
127.0.0.1
www.cammino-al-dente.net
127.0.0.1
sutterer.net
127.0.0.1
www.sutterer.net
255.255.255.255
broadcasthost
::1
localhost
fe80::1%lo0
localhost
Then I restarted Apache...But nothing happens :-(
I could reach my website cammino-al-dente.net only by using the Server Default-entry, chancing the entry to my cammino...-folder
Regards
Fred Mario

In the /etc/apache2/extra/httpd-vhosts.conf file check this line exists:
NameVirtualHost *:80
This solve same issue for me.
I hope it's help.

10.5.1 Broken Mail Server - virtual host configuration

Hi,
I have been trying to set up my mail server (new 10.5.1 build) to run with virtual hosts. I read pterobyte's tutorial ( Making Virtual Mail Users in OS X 10.4/10.5 Server) and implemented his suggested workarounds. However, it doesn't seem to have worked. I am now concerned that I have screwed things up beyond reprieve and need help to get it working again.
To give a start, I have included my postconf output below:
swallowtail:postfix serverconfig$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mapsrbldomains =
messagesizelimit = 10485760
mydestination = $myhostname,localhost.$mydomain,localhost,inovaplus.com
mydomain = inovaplus.com
mydomain_fallback = localhost
myhostname = swallowtail.inovaplus.com
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost = mailfilter.fastnet.co.uk
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permit_mynetworks rejectrblclient sbl-xbl.spamhaus.org rejectrblclient zen.spamhous.org permit
smtpdpw_server_securityoptions = none
smtpdrecipientrestrictions = permitmynetworks,reject_unauthdestination,permit
smtpduse_pwserver = no
unknownlocal_recipient_rejectcode = 550
virtualaliasdomains = hash:/etc/postfix/virtual_domains
virtualaliasmaps = hash:/etc/postfix/virtual
virtualmailboxdomains = hash:/etc/postfix/virtual_domains
virtual_transport = lmtp:unix:/Volumes/Private/Mail/socket/lmtp

Same issue here. I am current on all system updates. I have noticed this with any photoshop cs3 jpeg file. When using "mail", attached photoshop jpeg files show up as a plain text document "What???" Using Automator produces the same results. I did not have this problem with 10.5.1. I can't mail out any photoshop jpeg files?!@%* I just got off the phone with apple tech support and they told me that Adobe has not yet updated their software to comply with Leopard. Come on. Cover flow in Leopard 10.5.2 is still not working with Adobe photoshop jpeg files either. They Still show up pixelated. Yes, I know the work around by going into photoshop/preferences/file handling/image previews: Never Save. Yea, sure that works, but that is something that not any Mac user should have to do. I have had more problems dealing with pictures on my Mac than my Pc by far. Anybody else? Solution? Better Operating System?

Tomcat 4.0.1 & Apache 1.3.22 & mod_webapp & virtual hosts

I have succesfully been able to get tomcat 4.0.1 and apache 1.3.22 to use mod_webapp in both linux and windows.
First problem:
If I don't include a trailing slash, my webapp will not display. Just a 404. mod_dir works on the apache end. Also if I access my context thru tomcat on port 8080, without a trailing slash, it will put one in for me. Only when using mod_webapp, it doesn't seem to work.
So...
http://localhost/examples <--- doesn't work
http://localhost/examples/ <--- works
Second problem:
How can I get virtual hosts working with mod_webapp? I've successfully been using mod_jk for a while now with virtualhosts, but there are no instructions on how to do this with mod_webapp. Has anyone been able to do this? Is it even possible? Is there a way to alias a /webapp to '/' or something?
Any help/suggestions are appreciated,
Tom

Unfortunately, Tomcat 4.0.1 use the port number 8180 as default. Just after the installation, you need to test it by typing:
http://localhost:8180/
If the index page of Tomcat appears, then you succeed.
On linux platform the webapps directory need to be downloaded for a separate package. For downloads, please visit here:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/rpms/tomcat4-webapps-4.0.1-1.noarch.rpm
Such webapps should be installed in {TOMCAT_HOME}/webapps. After all, just restart the Tomcat server (as I know) and see the results by typing:
http://localhost:8180/
Click on the link to see further examples.
Good luck!

How to create a new virtual host under tomcat 4.1.x?

hi all
i need some help creating a new virtual host under tomcat 4.1.18!
that's what i do:
i'm using the web configuration, reacheable by typing "http://localhost:8080" and then clickign administration
i create a new host
name: www.class-site.it
application base: webapps\class-site
then i create the context:
document base: webapps\class-site
path: /
and nothing works!!!
anyone could help me?
if needed i can also post the server.xml file
thanx in advance for your help
sandro

It should look like this
<Host name="myvhost.com" debug="0" appbase="/my/path/to/webapps" unpackWars="true">
<Context path ="" docBase="ROOT" debug="0"/>
</Host>
This should be inside the <Engine> tags. You should be able to access a page by going to
http://myvhost.com:8080/index.jsp
Obviously you need index.jsp in /my/path/to/webapps/ROOT/index.jsp
Hope that helps

Web sharing - virtual hosts and CGI

This topic might be a bit advanced for this forum, I'm not sure. But here goes.
I'm trying to set up my laptop to act like a web server so that I can do test development on it. I have two web sites, and have successfully created virtual hosts for each of them.
The part that I'm struggling with now is enabling CGIs, as I want to learn to write CGIs in Perl. I can't seem to find any site that discusses how this is done in Leopard. One said something like "just put the CGIs into /Library/WebServer/CGI-Executables and it'll work", but of course, since I've got virtual hosts defined, it seems that anything addressed to "localhost" defaults to the first virtual host and thus there is no way to refer to a CGI placed in that location. Besides which, I'd like to know how to enable CGIs placed in a folder on each of my virtual sites, so that I could test them in place.
Any ideas?

One said something like "just put the CGIs into /Library/WebServer/CGI-Executables and it'll work", but of course, since I've got virtual hosts defined, it seems that anything addressed to "localhost" defaults to the first virtual host and thus there is no way to refer to a CGI placed in that location.
That is an incorrect assumption.
By default, Apache is configured to recognize any URI that begins with /cgi-bin and serve that request via a CGI script in /Library/WebServer/CGI-Executables
This is true even though each site's DocumentRoot is set somewhere else on the file system (that's by design since it makes it harder for a remote attacker to affect your CGIs)
Since it does not matter which site the request was on, any /cgi-bin request would be served from there, so:
http://www.domain1.com/cgi-bin/some.cgi
http://www.domains2.net/cgi-bin/other.cgi
would both be served from /Library/WebServer/CGI-Executables even though they are for two different virtual hosts.
Now, of course, if you want each site to be separate and have its own set of CGIs (maybe some.cgi for domain1 does something different from some.cgi on domain2) then this approach causes problems. For this you will need to edit each site to have its own cgi-bin directory.
Unfortunately (although I haven't tested it) I think Matt's solution won't work because Apache is going to catch all /cgi-bin/ requests and serve them from /Library/WebServer/CGI-Executables, never getting to the cgi-bin directory within each site's documentroot.
To set site-specific CGI directories you need to add a ScriptAlias command to each site's .conf, such as:
ScriptAlias /cgi-bin/ /path/to/site/cgi-bin/
This tells apache that any request for /cgi-bin/* should be served from /path/to/site/cgi-bin
Ideally the path should be outside of the site's normal document root, but it can be inside if you really want.

Virtual Hosts vs Localhost

Similar Messages

Maybe you are looking for