Virtual Hosts & Port Redirections

Hi guys,
In 10.6 i used to be able to setin the Server Admin GUI settings for the web service. This included Virtual Hosts & Port Redirections. How do i go about doing this on 10.7?
For example, I need myserver.mycompany.com:80 to redirect to myserver.mycompany.com:8088 & mygreatsite.company.com:80 to redirect to mygreatsite.company.com:9006.
Both of which are hosted on myserver.mycompany.com.
Links apprecaited.. i'm guessing i'm in for an Apache lesson?

I hope that article helps you, maybe you can figure it out and post back for the rest of us!
I haven't actually read it yet, I just saved it to my Pinboard page for later, because I know eventually I will have to deal with vhosts in Lion.

Similar Messages

WDA application on virtual host (port)

Hi,
is there a way how to deploy (create) a webdynpro application on a virtual host (port)? As I generate a webdynpro application, SAP creates a service under default host (port). I need to have my application accessible only on virtual host (port) - different to default. Therefore alias cannot be used. I haven't found any parameter how to set this port when I create a WDA application in SE80.
I'm looking for some system setting or configuration, not application solution.
Thanks.
Petr

Without adding a virtual host, did you try using the following arrangement?
Port 80
Listen 77777
No virtual host is used here assuming you have only one application - which is this form application whose physical port is 7777.
thanks,
AMN

Virtual hosts all redirect to first in list - Snow Leopard Server

I know this is something that's been talked about here before, but I don't see the answer that's making it work for me.
Basically, I am trying to use virtual hosts in a pretty standard fare way. I'm just making a bunch of subdomains: wiki.mysite.com, client1.mysite.com, client2.mysite.com, you get it.
All of these resolve fine, but they're all showing wiki.mysite.com (the first in the list in Server Admin). If I reorder the list, I get whatever's first. I do not have a * in the aliases section of any of these sites.
Can anyone help?

Server manager and workgroup manager in some cases (apache) reads and writes out to files, so you can check if SM is doing the right thing by apache if you go to the actual files in /etc/apache2/sites and check what is there...
i DID have this behavior and fixed it by putting something in the alias part of server manager - i guess it is worth a try and you can always take it out again.

Virtual host redirection

Hi All,
We have a web site based on oracle portal and two virtual hosts have been defined in httpd.conf file as follows:
<VirtualHost *:7779>
ServerName www.mycompany.com
Port 80
ServerAdmin [email protected]
RewriteEngine On
RewriteOptions inherit
OssoConfigFile /opt/oracle/product/portal_int/Apache/Apache/conf/osso/osso_www.conf
OssoIpCheck off
</VirtualHost>
<VirtualHost *:7779>
ServerName abc.mycompany.com
Port 443
AddCertHeader HTTPS
ServerAdmin [email protected]
SimulateHttps On
RewriteEngine On
RewriteOptions inherit
RewriteRule ^/$ /portal/page/portal/MyHome [PT]
OssoConfigFile /opt/oracle/product/portal_int/Apache/Apache/conf/osso/osso_abc.conf
OssoIpCheck on
</VirtualHost>
Now when a request for abc.mycompany.com/PublicPages is made the request gets redirected to www.mycompany.com/PublicPages while the request for abc.mycompany.com/PrivatePages (requiring authentication) is served by abc.mycompany.com/PrivatePages itself.
I want to know:
1> How can I configure this type of behaviour for name based virtual hosts so that request for abc.mycompany.com/PublicPages is served by abc.mycompany.com/PublicPages itself and doesn't get redirected to www.mycompany.com/PublicPages.
2> Where can I find the URL mappings for pages in the Oracle portal.
3> How can I control the redirection of requests in general, on the basis of name based virtual hosts.
Regards,
Noaman

Hi,
Thank you for posting in Windows Server Forum.
From the listed error it seems that there is RD Virtualization Host process get failed and user authentication redirection can’t occur successfully. Because it seems that there might be some configuration issue during your RDVH configuration. So if possible
please check the whole configuration again and see whether it can resolve your issue. You can refer beneath article for rechecking.
Lab Ops 6 – Setup VDI in Windows Server 2012R2
http://blogs.technet.com/b/andrew/archive/2013/10/14/lab-ops-6-setup-vdi-in-windows-server-2012r2.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Move just wikis to new Lion server (redirect one virtual host)

I have a bunch of services on my Mac Pro with Snow Leopard Server, including file sharing, VPN, subversion, wikis, several websites, a few webapps, etc. I don't want to upgrade that server right now, but I'd like to try upgrading the wikis to Lion Server and Wiki Server 3.
How could I move the wiki's to Lion Server on another machine? They are all accessed through a seperate virtual host.
We only have one public IP right now (I maybe could get a second public IP but don't want to just for this.) Everything hits my router (dd-wrt device, so quite configurable) which sends port 80 (and most other ports) to my snow leopard server.
One idea would be to have the router redirect another port (8080 or something) to the new lion server, and then put a redirect page on the original wiki address (port 80) to redirect over to 8080, which would then go to the other server. But that's not really ideal because then the users of my wiki would see it on a new port and a lot of times ports other than 80 are blocked by firewalls (not my firewall, but firewalls closer to my users.)
So does anyone have an other ideas on how to redirect the traffic of one virtual host to another internal machine behind NAT?
Separate question: any experience migrating a wiki from Wiki Server 2 to Wiki Server 3? Did it work well?
John

The best way to do this is to take the contents of /Library/Collaboration and put it in a location accessible from your newly set up Lion install. In Server.app, enable Wiki, and run:
     sudo wikiadmin migrate -r /Path/To/Library/Collaboration
After that, start the wiki and you should be good to go. You should bind your Lion server to the same Directory as the Snow Leopard server, to ensure permissions and users carry across successfully.
    A.

Hiding the Port in a Virtual Host/Server-name Alias

I need some guidance/help with the HTTP Server in AS 10g. We have several new Portal sites with a mix of forms, reports, and pl/sql server pages. We wish to make these services available from the internet via an aliased hole in the firewall.
We have our public alias of Alias.CompanyWebsite.com mapped to the server-name, but we'd like to get the alias mapped to servername:port. I've tried to get this set up using virtual hosts in the HTTP server, but I'm having no luck. I'm also having trouble finding documentation on how to this.
Is there a way to hide the server-name and port number via a virtual host (alias) in HTTP Server and/or Web Cache? If so, how do you accomplish this?
Thanks,
Josh

Usually it is like this:
outside name: www.acme.com
oudside port: 80
inside name: inside.acme.local
inside port: 7778 (if you have a seperate machine for the middle tier)
In the Webcache you'll need a site
www.acme.com with port 80
and an origin server
inside.acme.local with port 7778
Then create a site-to-server mapping from www.acme.com to inside.acme.local
If your firewall listens to another name or does something with the ports you need to change the site accordingly.
cu
Andreas

What does virtual host and port mean in a system in ESB console

Hi !
When you click on a system in ESB console you can see and change 'cluster name' , 'Virtual host' and 'Port' .
What does this mean ?
As default the port is 8888 even though the installation uses port 80.
If I change the port, I see no difference.
Could someone please explain ?

It is used to generate the endpoint urls in the wsdl's for the services you have deployed. It needs to be set to the esb server and port number where the services are installed. So if your esb installation uses port 80 you need to change 8888 to 80. Try the wsdl and look at the url of the endpoint.
Kind Regards,
Andre

CT5760 - virtual-host in parameter-map not used in webauth redirect

Hi all.
I'll try posting my issue here before I post a TAC on this:
Cisco CT5760 wireless controller running IOS-XE version 3.6.0.
This issue is related to web authentication on an SSID with external web portal. It seems that the statement "virtual-host" in "parameter-map type webauth global" is not used as intended. I'll try to explain:
When a user connects to an SSID with external web authentication enabled and the user opens a web browser, the user will get redirected to the external web portal for authentication. In this redirect URL we see the parameter "switch_url=http://1.2.3.4/login.html". The IP address 1.2.3.4 is, in this example, our virtual IP. But we have also configured "virtual-host" to be webauth.example.com. And in my opinion the "switch_url" parameter should be "switch_url=http://webauth.example.com/login.html". This is how it works on our old Cisco WiSM1 implementation.
The reason why this is a problem is that the clients web browser will not accept the certificate installed on "http://1.2.3.4" because it is not issued with that IP address, only the hostname webauth.example.com. I know that it is possible to get certificates issued with an IP address (as long as it's not an RFC1918 IP address), but rumors say that many Certificate Authorities will stop issuing these soon, even with "real IPs". Therefore it is important that the redirect URL gets corrected.
Does anyone disagree with me that this is a bug?

Hi and thank you for your response.
I feel that I need to clarify a few things. Here is my parameter-map config (a bit edited):
parameter-map type webauth global
virtual-ip ipv4 1.1.1.1 virtual-host webauth.example.com
intercept-https-enable
parameter-map type webauth webauth_external
type webauth
redirect for-login https://webauth-external.example.com/v2/login.html
redirect portal ipv4 x.x.x.x
So the problem here is that a web browser of the client gets the following redirect URL:
https://webauth-external.example.com/v2/login.html?switch_url=https://1.1.1.1/login.html&redirect=http://www.cnn.com
Then after a successful login on the external portal, the user gets redirected back to https://1.1.1.1/login.html. Here is the core of my problem. I think that the parameter "switch_url" should be with the name webauth.example.com since I configured it as the "virtual-host". This is the behavior we see with our old Cisco WiSM1.
When the redirect goes to https://1.1.1.1/login.html the client complains about the certificate, because it is not issued to that IP address but to the hostname.
I can verify that the client does not complain about this if I manually edit the redirect URL on the client to the following:
https://webauth-external.example.com/v2/login.html?switch_url=https://webauth.example.com/login.html&redirect=http://www.cnn.com
Then the redirect after authentication goes to https://webauth.example.com/login.html and the client accepts the certificate and everything is peachy.
Do you see my problem? And yes, the virtual IP resolves to the name in DNS.

Configure Virtual Host to Listen on Two Ports

Oracle App Server 9.0.4
I need my mid-tier HTTP server to listen for SSL traffic on 2 ports: 443 and 4443. I also need it to listen for non-SSL traffic on port 80 (this traffic should only come from localhost).
We have an SSL certificate for our web address already and unfortunately it will take quite a while to get another certificate, so I'd prefer not to have to setup a different url for the second SSL port if I can help it.
Currently there is one virtual host set as type default.
The Virtual Hosts properties page provides the following 3 options for Listening Ports (host is set for https protocol):
(1) Listen on all main ports
(2) Listen on specific port (443 by default)
(3) Listen only on the main server default port
If I set it to option (1) then the server will not respond on port 80 for non-SSL traffic.
If I set it to option (2) then it will not respond to ssl traffic on port 4443.
If I set it to option (3) then it is listening on port 80 only (the default port for the HTTP server)
Is there a way to have this default virtual host listen to both 443 and 4443 for SSL traffic and non-SSL traffic on 80?
Appreciate your time.
Message was edited by:
dredstar

Thanks for the reply Kjell, I ended up doing the same thing. I left my default host servicing all ports with https, so it would respond to incoming requests on ports 443 and 4443. Then I created a new http protocol virtual host listening only on 127.0.0.1 port 80 and that allowed non-SSL traffic to be serviced coming from the machine itself.

IP Virtual Host w/SSL serving on port 80 and 443

We have an OS 10.3.8 system and we've configured several virtual hosts using the system admin panel. One IP has several hosts on it. We have a seperate IP with one virtual host on it since it is running SSL. I have it configured for port 443 and I have all the security certificates installed OK. The site operates correctly over HTTPs. If I try to access it with standard HTTP I get a service not available error (which makes sense since server admin sets the config files to port 443 ... not 80).
The only way I can get it to work is to add another virual host in server admin running on that IP at port 80. Unfortunately, that means it will be logged seperately (which I don't really want it to do). What do I need to change to get a single virtual host on a specific IP to respond correctly to both 443 and 80 using the file layout generated by server admin (I can modify them manually)?
Thanks in advance ...
Tom

>The only way I can get it to work is to add another virual host in server admin running on that IP at port 80.
That's correct. That's how you run a site as both HTTP and HTTPS - they're two sites.
> Unfortunately, that means it will be logged seperately
Why? You can set both sites to use the same log file and their hits will be combined in a single file.
> What do I need to change to get a single virtual host on a specific IP to respond correctly to both 443 and 80 using the file layout generated by server admin (I can modify them manually)?
You can't, but if your issue is the logging, my answer above should take care of that.

Multiple IP vs Same IP multiple port for virtual hosts

Anyone have any recommendations or experience in setting up a virtual host that has a listener for each site?
The issue is when I have to restart a single site, I have to restart them all, because they are installed under the same listener/server.
I need a setup where I can install and manage each website (on the same box) on it's own listener/server instance so re-starting one site doesn't effect another.

Add a service in the Network preference pane. Select the network interface you want; e.g., Ethernet. Configure as desired. Apply and test.

Oracle Portal Virtual Host Enhacement for Multiple Virtual Hosts

I open the TAR Number: 4326752.996
The TAR is related to " REQUEST ASSISTANCE FOR MULTIPLE VIRTUAL HOSTS AND MULTIPLE PAGE GROUPS CONFIG. "
This is the Scenario: We Have Oracle Portal installed in a single Box. yes I know I know... but Not everybody is Yahoo or Google for Clusters and all the good stuff, we just want our website managed by Oracle Portal since all our ERP is running Oracle Database. Anyway. 1 Box running Oracle Portal Infrastructure and MidTier.
It turns out that our previous configuration we have the LAMP Solution with PHP, Apache with Virtual Servers configuration very trivial for a regular web server however we have about 6 Virtual domains.
For example:
www.abc.com
www.def.com
www.ghi.com
www.jkl.com
www.mno.com
www.pqr.com
We also like to post all our Intranet Information in this great Portal:
http://intranet.com
Where intranet.com is the same server but setup in our Internal DNS without be a Real Internet Register Domain.
So bottom line we start doing great with Install our single box install, later [GRRRRRR does not come by default in port 80 GRRRRRR, ok need to move and setup the virtual host to resolve our main External website www.abc.com ]
For starters ok it worked we have our main website running Oracle Portal.
Now is time to go to the step number 2.
Setup another Page Group in Portal to be the Page_Group_INTERNAL.
I figure if Apache can setup Virtual Hosts pointing to Independent parts of the File System without be shared. I was expecting some kind of custom configuration where I can setup httpd.conf to point to some specific PageGroups to make sure
www.abc.com => Page_Group_External
never share information with:
intranet.com => Page_Gorup_Internal
My TAR was very quick closed with the Argument that is not what It supposed to do.
Since a virtual host is a common thing to do on Linux and Apache, I wonder if You guys could list this as one of the default features to have multiple virtual domains assosiated with Page Groups that they never talk or share Resources I think that would be really great.
In the mean time I guess we have no option but to put a password for every internal page or take the risk of share our Information to the Internet. Perhaps designate another box with Oracle Portal but In that case Is not really cost/bennefit to use a killer technology for our external site since we just have no more than 30 pages.
Anyway just figure drop you guys a note any advise will be really appreciated.
Best Regards Dino.

Hi Martin,
1. To change the target URL of KM resources you can to the following:
Access the URL Generation Service Configuration by navigating to:
System Administration -> System Configuration -> Knowledge Management -> Configuration
Content Management -> Global Services -> URL Generator Service
Change the Host property to "portal.company.com".
2. You change the Port by opening the Visual Administrator and going to : Dispatcher -> Services -> HTTP Provider
Change there the "Ports" entry from (Port:50000,Type:http)to (Port:80,Type:http). Then go on "Save".
3. To remove the "/irj" from the portal URL you can create a index.jsp with the following content, and save it in the J2EE Documentation folder:
<Drive>:\usr\sap\<SAPSID>\JC<J2EE_instance_number>\j2ee\cluster\server0\apps\sap.com\com.sap.engine.docs.examples\servlet_jsp\_default\root
<%
//Send the redirect using server redirection (not client script)
//This will also send the HTTP GET parameters
String queryString = request.getQueryString() ;
if (queryString==null ) {
response.sendRedirect
("irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default") ;
} else {//redirect with HTTP GET parameters
response.sendRedirect
("irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default?" + queryString) ;
%>
Hope this helps,
Robert

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/*"

Virtual Hosts, lookupd and loopback address

For days I've been trying to install and configure MySQL, phpMyAdmin and virtual hosts, but I just seem to be digging myself a deeper hole. I decided to focus on virtual hosts first and learned how to modify my httpd.conf, hosts and NetInfo files, only to discover that I also have to modify something called lookupd, which I can't even find.
I posted a rather detail query at http://discussions.apple.com/thread.jspa?messageID=4232285#4232285
and received this reply:
[QUOTE]I'm not real sure it applies to virtual domains, but if you want your local machine to redirect URLs to a local domain you need to set up lookupd. . . . As it is, your browser is not even finding Apache because you have no DNS server. As an expedient alternative most people use the loopback address with a custom port number, but you are more demanding than that.[/QUOTE]
Maybe you should repost in the UNIX section and use a better subject line. This is pretty geeky stuff.[/QUOTE]
So is it true that I've been beating my brains out when there's a simpler method involving a loopback address with a custom port number? If so, can someone tell me how to do it or direct me to a tutorial? If, instead, I have to modify this lookupd file, how do I find it? I can't find it with Spotlight, and I haven't been able to locate it with TextWrangler yet.
Thanks!

You should ask this question at http://discussions.apple.com/forum.jspa?forumID=735&start=0

Virtual hosts/HTTPS

Using WL 6.0, we're setting up multiple virtual hosts, hosted off a
single
WL cluster.
We want HTTPS access to these sites, so I assume each virtual host needs
to be configured with its own Certificate, right ?
Can I setup one of these virtual hosts to request client side
Certificates
(2-way authentication) as well ?
Also, can I set a list of trusted CAs, not just one ?
thanks
-john

Because of the nature of HTTPS/SSL, you can't do name-based HTTPS virtual hosting - all the SSL connection work is done before Apache can tell what site the user was aiming for. Therefore, any connection on port 443 is going to go to the same virtual server, regardless of the hostname entered by the user.
Your best solution is to use different IP addresses on the server, binding www.example1.com ports 80 and 443 to one IP address and binding www.example2.com to the other IP address. Whether this is practical for you depends on your network setup (if you only have one public IP address, for example, then it's not going to work for you either.
Failing that you can add a check to the port 443 site to ensure that the user requested the domain you expect. This wouldn't prevent a user from opening a connection to https://www.example2.com and getting a SSL certificate error, but at least you could redirect them back to the non-https site.
Adding something like this towards the end of the .conf file for the https site should help:
RewriteCond %{HTTP_HOST} !^www.example1.com$ \[NC\]
RewriteRule ^.*$ http://%{HTTPHOST}%{REQUESTURI} [R]
This somewhat cryptic setup first checks whether the request is for www.example1.com. If it is not (thanks to the !) then it rewrites the URL using http rather than https and sends the user a redirect.

Virtual Hosts & Port Redirections

Similar Messages

Maybe you are looking for