Using different DocumentRoot directive within virtual hosts

We have installed Oracle iAS 9i with default settings and created two VirtualHosts in Apache httpd.conf file with two different document root directories.
We figured out that static http content served by Apache itself appears correctly, but JSP requests go to the wrong document root.
For example after you restart Apache server the request for the first virtual host goes correctly, but the request for the second one does not; it uses previous document root.
We really need information if there is a solution somewhere or it's a bug.

Let me try again the program eat some of the content:
nameVirtualHost 10.1.1.1
# Remove the \ on the next line
\<VirtualHost 10.1.1.1\>
ServerName devserver
DocumentRoot "c:\Dev"
# Remove the \ on the next line
\</VirtualHost\>
# Remove the \ on the next line
\<VirtualHost 10.1.1.1\>
ServerName testserver
DocumentRoot "c:\Test"
# Remove the \ on the next line
\</VirtualHost\>
null

Similar Messages

Virtual Hosts in Apache HTTP Server

How to configure virtual hosts in Apache HTTP Server httpd.conf file.
If I want to access my server with some other name(alias), how can I do this ?
Suggestions in this matter would be highly helpful.
Thanks
Vidhyut Arora

Following is a note explaining how to setup
Virtual hosts.
Hope this helps
Ranga
Note:70647.1
Subject: Apache Server Virtual Hosting
Last Revision Date: 07-JUN-2001
PURPOSE
This document discusses considerations for setting up virtual hosts on an
Apache machine, to include how to get the hostname working and how to
configure Apache.
SCOPE & APPLICATION
The information in this document is intended for those who manage multiple sites
using an Apache machine.
REFERENCES
First published in Apache Week issue 31 (6th September 1996)
Last update 20th September 1998
Using Virtual Hosts
Virtual Hosts let you run multiple independent Web sites on a single host with
a single Apache setup.
One of the most important facilities in Apache is its ability to run virtual
hosts. This is now the essential way to run multiple Web services - each with
different host names and URLs - that appear to be completely separate sites.
This is widely used by ISPs, hosting sites and content providers who need to
manage multiple sites but do not want to buy a new machine for each one.
Picking an IP address
There are two types of virtual hosts: IP-based and non-IP-based. The former is
where each virtual host has its own IP address. You must have a new IP address
for each virtual host you want to set up, either from your existing allocation
or by obtaining more from your service provider. When you have extra IP
addresses, you tell your machine to handle them. On some operating systems, you
can give a single ethernet interface multiple addresses (typically with an
fconfig alias command). On other systems, you must have a different
physical interface for each IP address (typically by buying extra ethernet
cards).
IP addresses are a resource that costs money and are increasingly difficult to
get, so modern browsers can now also use 'non-IP' virtual hosts. This
lets you use the same IP address for multiple host names. When the server
receives an incoming Web connection, it does not know the hostname that was used
in the URL. However, the new HTTP/1.1 specification adds a facility where the
browser must tell the server the hostname it is using, on the Host: header. If
an older browser connects to a non-IP virtual host, it does not send the Host:
header, so the server must respond with a list of possible virtual
hosts. Apache provides some help for configuring a site for both old and new
browsers.
Picking a Hostname and Updating the DNS
Having selected an IP address, the next stage is to update the DNS so that
browsers can convert the hostname into the right address. The DNS is the system
that every machine connected to the internet uses to find the IP address of host
names. If your hostname is not in the DNS, no one can connect to
your server (except by the unfriendly IP address).
If the virtual hostname you are going to use is under your existing domain,
you can just add the record into your own DNS server. If the virtual hostname
is in someone else's domain, you must get them to add it to their DNS
server files. In some cases, you want to use a domain not yet used on the
internet, in which case you must apply for the domain name from the
InterNIC and set up the primary and secondary DNS servers for it, before adding
the entry for your virtual host.
In any of these cases, the entry you need to add to the DNS is an address record
(an A record) pointing to the appropriate IP address. For example, say you want
the domain www.my-dom.com to access your host with IP address 10.1.2.3: you
must add the following line to the DNS zone file for my-dom.com:
www A 10.1.2.3
Now, users can enter http://www.my-dom.com/ as a URL in their browsers and get
to your Web server. However, it will return the same information as if the
machine's original hostname had been used. So, the final stage is to tell Apache
how to respond differently to the different addresses.
How Apache Handles Virtual Hosts
Configuring Apache for virtual hosts is a two-stage process. First, it needs
to be told which IP addresses (and ports) to listen to for incoming Web
connections. By default, Apache listens to port 80 on all IP addresses of the
local machine, and this is often sufficient. If you have a more complex
requirement, such as listening on various port numbers, or only to specific IP
addresses, then the BindAddress or Listen directives can be used.
Second, having accepted an incoming Web connection, the server must be
configured to handle the request differently, depending on what virtual host it
was addressed to. This usually involves configuring Apache to use a different
DocumentRoot.
Telling Apache Which Addresses to Listen To
If you are happy for Apache to listen to all local IP addresses on the port
specified by the Port directive, you can skip this section. However, there are
some cases where you want to use the directives explained here:
- If you have many IP addresses on the machine but only want to run a Web
server on some of them
- If one or more of your virtual hosts is on a different port
- If you want to run multiple copies of the Apache server serving different virtual
hosts
There are two ways of telling Apache what addresses and ports to listen to:
- Use the BindAddress directive to specify a single address or port
- Use the Listen directive to any number of specific addresses or ports
For example, if you run your main server on IP address 10.1.2.3 port 80, and a
virtual host on IP 10.1.2.4 port 8000, you would use:
Listen 10.1.2.3:80
Listen 10.1.2.4:8000
Listen and BindAddress are documented on the Apache site.
Configuring the Virtual Hosts
Having gotten Apache to listen to the appropriate IP addresses and ports, the
final stage is to configure the server to behave differently for requests on
each of the different addresses. This is done using <VirtualHost> sections in
the configuration files, normally in httpd.conf.
A typical (but minimal) virtual host configuration looks like this:
<VirtualHost 10.1.2.3>
DocumentRoot /www/vhost1
ServerName www.my-dom.com
</VirtualHost>
This should be placed in the httpd.conf file. You replace the text
10.1.2.3 with one of your virtual host IP addresses. If you want to specify a
port as well, follow the IP address with a colon and the port number
(example: 10.1.2.4:8000). If omitted, the port defaults to 80.
If no <VirtualHost> sections are given in the configuration files, Apache
treats requests from the different addresses and ports identically. In terms of
setting up virtual hosts, we call the default behavior the main server
configuration. Unless overridden by <VirtualHost> sections, the main server
behaviour is inherited by all the virtual hosts. When configuring virtual
hosts, you must decide what changes to make in each of the virtual
host configurations.
Any directives inside a <VirtualHost> section apply to just that virtual host.
The directives either override the configuration give in the main server, or
supplement it, depending on the directive. For example, the DocumentRoot
directive in a <VirtualHost> section overrides the main server's DocumentRoot,
while AddType supplements the main server's mime types.
Now, when a request arrives, Apache uses the IP address and port it arrived on
to find a matching virtual host configuration. If no virtual host matches the
address and port, it is handled by the main server configuration. If it does
match a virtual host address, Apache uses the configuration of that virtual
server to handle the request.
For the example above, the server configuration used is the same as the
main server, except that the DocumentRoot is /www/vhost1, and the
ServerName is www.my-dom.com. Directives commonly set in <VirtualHost>
sections are DocumentRoot, ServerName, ErrorLog and TransferLog. Directives
that deal with handling requests and resources are valid inside <VirtualHost>
sections. However, some directives are not valid inside <VirtualHost> sections,
including BindAddress, StartSevers, Listen, Group and User.
You can have as many <VirtualHost> sections as you want. You can
leave one or more of your virtual hosts being handled by the main server, or
have a <VirtualHost> for every available address and port, and leave the main
server with no requests to handle.
VirtualHost sections for non-IP Virtual Hosts
Non-IP virtual hosts are configured in a very similar way. The IP address that
the requests arrive on is given in the <VirtualHost> directive, and the
host name is put in the ServerName directive. The difference is that there
(usually) is more than one <VirtualHost> section handling the same IP address.
For Apache to know whether a request arriving on a particular IP
address is supposed to be a name-based requests, the NameVirtualHost directive
addresses for name-based requests. A virtual host can handle more than one
non-IP hostname by using the ServerAlias directive, in addition to the
ServerName.
null

[SOLVED] I can't get virtual hosts working. What's wrong?

What I've decided to do is try to set up each domain name in the user folder to whom it belongs (for example: /home/username/somedomain.com/htdocs). I can't get it to work though. I keep getting an error saying that there's no index file (although there is) or that the location isn't readable (although it is). I'm trying to make it so that if the domain name matches with a virtual host section in httpd-vhosts.conf that a specific DocumentRoot will be loaded for that domain, etc. But, if the domain name points to my server but doesn't match, then I want the default location to work. I can't seem to make this work.
This is my http.conf:
ServerRoot "/etc/httpd"
Listen 80
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
LoadModule substitute_module modules/mod_substitute.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule log_forensic_module modules/mod_log_forensic.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
LoadModule proxy_module modules/mod_proxy.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 proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule ssl_module modules/mod_ssl.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule cgid_module modules/mod_cgid.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
#CUSTOM
LoadModule php5_module modules/libphp5.so
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
User http
Group http
</IfModule>
</IfModule>
ServerAdmin [email protected]
DocumentRoot "/srv/http/default/htdocs"
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>
<Directory "/srv/http/default/htdocs">
Options Indexes FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>
<IfModule dir_module>
DirectoryIndex index.php,index.html
</IfModule>
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>
ErrorLog "/var/log/httpd/error_log"
LogLevel warn
<IfModule log_config_module>
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>
CustomLog "/var/log/httpd/access_log" common
</IfModule>
<IfModule alias_module>
ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
</IfModule>
<IfModule cgid_module>
#Scriptsock /var/run/httpd/cgisock
</IfModule>
<Directory "/srv/http/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
DefaultType text/plain
<IfModule mime_module>
TypesConfig conf/mime.types
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
</IfModule>
# 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
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
#CUSTOM
Include conf/extra/php5_module.conf
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
And here's my httpd-vhosts.conf:
NameVirtualHost *:80
<VirtualHost *:80>
ServerName 45.117.5.40
ServerAdmin [email protected]
DocumentRoot "/srv/http/default/htdocs"
ErrorLog "/srv/http/default/log/error_log"
CustomLog "/srv/http/default/log/access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerName somedomain.com
ServerName www.somedomain.com
ServerAdmin [email protected]
DocumentRoot "/home/normaluser/somedomain.com/htdocs"
ErrorLog "/home/normaluser/somedomain.com/log/error_log"
CustomLog "/home/normaluser/somedomain.com/log/access_log" common
</VirtualHost>
So, for example, I want it to be so that if I visit http://45.117.5.40 that it'll show the stuff ftom /srv/http/default/htdocs but if the domain name matches somedomain.com then I want the server to show the content from /home/normaluser/somedomain.com/htdocs.
What currently happens is that if I visit http://45.117.5.40 or somedomain.com, they both show the same content from /srv/http/default/htdocs.
If I comment out the first VirtualHost section, then everything stops working and I see the default "Access forbidden!" message.
What am I doing wrong?
Last edited by trusktr (2012-04-13 06:15:41)

I fixed it. In case any newbs come across this, I had to add a new <Directory> section for the DocumentRoot of the virtual host. Simply adding the VirtualHost entry in the vhosts file isn't enough.
For example, for the "somedomain.com" vhost in the example above to work, I added this to http.conf:
#This must match with the same location as DocumentRoot in httpd-vhost.conf.
<Directory "/home/normaluser/somedomain.com/htdocs">
#Put whatever directives you want in here
Options Indexes FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>
Let me know if you need any clarification.
Last edited by trusktr (2012-04-13 06:16:02)

Setting up Virtual Hosts on a Snow Leopard Development Server

Hi Everybody,
I'm losing hair over this - I thought it would be simple!
I have set up a Mac Mini Server running SLS and would like to host multiple websites for development on the internal network. I require the websites to be stored anywhere on the server, not just in Library/WebServer/Documents/. Ideally, I would like to access them by example.com/mynewsite so I don't have to mess around with DNS.
Currently I'm setting up websites in the Server Admin Web panel but it just doesn't work. I've noticed the error log keeps looking for files located in the Library/WebServer/Documents/ folder even though I have specified a different folder.
What Am I missing? Does anybody know of a tutorial / guide to point out potential issues when setting up virtual hosts? I have checked Apple's guide but it doesn't really help me. Any pointers would be much appreciated!
Cheers

Sites is likely failing here because Sites is based on the DNS and on the HEAD command within the http stream; if the DNS does not match, you won't get to the host, and if the HEAD command doesn't match the entry in the site, then you'll either get the * wildcard or (if no *) you won't be transferred to the target Site.
Check the web server logs, as a start.
If you want to see how this stuff works at the protocol level, you could telnet to port 80 and toss a http 1.1 GET / command and see what you get back for a page.
Per [rfc2616|http://tools.ietf.org/html/rfc2616], this sequence looks like this:
+telnet www.example.com 80+
then:
+GET / HTTP/1.1+
+host: www.example.com+
followed by two presses of the return key, and where www.example.com is your target Site (virtual host) name.
Alternatives to using DNS and virtual hosts are port-based hosting (which is easy), and you can also use IP addresses to establish virtual hosts. The former is set up via the Sites stuff, with various other ports being used for the web servers. Ugly, but easy. The IP-based approach can get ugly fast, too.
If you get DNS going and aliases added, and all this goes away in a puff of greasy orange smoke.

Virtual Host Mail Accounts Not Working

Hi. I have attempted to search the discussions for an answer to this, but haven't had much luck.
I have one server running 10.5.8. This server hosts 4 domains, 1 main and 3 virtual. Each domain needs an [email protected] email address. I have created a user in WGM named info and have created the short names for each domain: info (I assume the local domain short name doesn't need the domain.com added), [email protected], [email protected] and [email protected] I have entered the 3 virtual hosts in Server Admin-->Mail-->Settings-->Advanced-->Hosting-->Enable Virtual Hosting section.
The issue is that when I configure Mail for each of the accounts, they are being treated as though they are aliases and not virtual host accounts. In other words, each account sees the exact same mail. When I check Server Admin-->Mail-->Maintenance-->Accounts I do NOT see the three additional virtual host accounts, so clearly they are not being created.
This same server is also the mail server, so each domain's DNS MX record is pointing to this server. Like I said, I can send and receive mail, but it goes to all the accounts simultaneously (as aliases would) rather than individually.
I've scoured the documentation, but cannot seem to find what I have missed here to prevent this from working as it should.
Does anyone have experience with a successful deployment of a situation similar to this one?

I do, indeed, have the addresses set up for one user, as you have ascertained. I suppose that I will alter the setup in the manner in which you describe. What is completely perplexing to me is that if you review Apple's documentation just after the section after describing Mail Forwarding (~pg. 37) you will see that Apple is saying I can set it up the way I have. Directly from the text as follows:
Virtual hosting is a method you can use to host more than one domain name on the
same computer and IP address, with overlapping mail user names.
For instance, a mail server can receive mail transfer requests for two domains,
mail.example1.com and mail.example.com, both of which resolve to the same IP
address. For mail.example1.com, the server would deliver mail to “[email protected]”
to a user mailbox for “bob,” while it would also deliver mail to “[email protected]” to
a different user mailbox. Virtual hosts are essentially the converse of local host aliases.
Again, I state that if this is to be true, then I should have the ability to assign one Open Directory account and give that account the four addresses as above with each having a separate user mailbox. The way it is behaving now is like aliases, not virtual hosts as Apple describes.
I'd love to understand why this is the case, perhaps I'm completely misunderstanding the text.
Thanks again for the help, I'll just create 4 accounts, easy enough.

PHP "Virtual Host" 3/4% Correct, but Still error?

PHP "Virtual Host" Site error Using Dreamweaver
I created a virtual host on my local machine. I am using Apache, php5, and mysql 5. I moved my "wordpress files and
folders" into the root folder for my site. My htdocs looks like this;
<VirtualHost *:80>
ServerName localhost
DocumentRoot "C:/Program Files/Apache Group/Apache/htdocs"
</VirtualHost>
<VirtualHost *:80>
ServerName myvirtualrootfolder.com
DocumentRoot "C:/Program Files/Apache Group/Apache/htdocs/myvirtualrootfolder"
<Directory "C:/Program Files/Apache Group/Apache/htdocs/myvirtualrootfolder">
    Options FollowSymLinks Indexes
    Allow from all
    Order allow,deny
    AllowOverride All
</Directory>
</VirtualHost>
I followed the dynamic dreamweaver setup. Next I see, "This page may have dynamically-related files that can only be
discovered by the server. When I click "Discover", I'm told "my site definition isn't correct." Can anyone help me
please?

>Sorry. I just never get any help here
Really? Doesn't look that way to me:
http://forums.adobe.com/people/buffbill?view=overview
Other than a post from last week, and those you just posted within the past few hours....it looks like you are getting replies. I'm just sayin.

Virtual Host on WebLogic Server 5.1

I need to configure my weblogic server 5.1 on windows 2000 server to make a virtual
host address.
How I can do it ????
Thanks a lot for any help.
Bye

Hi Andy,
I think a good approach for you would be to use a proxy server --
browser -> proxy that supports virtual hosting -> WebLogic
Use a proxy which supports virtual hosting, and which can have a separate
certificate bound to each virtual host.
That way you can do SSL between the browser and the proxy, and you can
have the proxy do cleartext to WebLogic.
This situation gets around WebLogic's limitation of allowing only one
certificate per instance of the server.
You could also use 5.1 as the proxy in the following manner:
Run 3 instances of Weblogic, each as a proxy server, each bound to a
different IP address and DNS name, having its own certificate --
one instance for aaa.com, another for bbb.com, and a third for ccc.com
Then have each of these three instances of WebLogic proxy to your "app
server" instance of WebLogic on the backend.
Hope this makes sense.
Joe Jerry
Andy Walker wrote:
Hello,
I am tasked with implementing a virtual hosting situation that must
use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
and https://www.ccc.com all having separate IPs. These URLs must
forward the request to the same WebLogic Server instance. The problem
is each URL must have its own certificate while WLS 5.1 only uses one
certificate per instance.
I was thinking about using a proxy server such that all three Web
servers that would host the URLs would be sent to a proxy server which
would redirect to the WLS 5.1 instance.
My questions are, would this be feasible using WLS 5.1 as the Web
Server and again WLS as the App Server? How secure is this
arrangement? Is it preferable to use another vendor's software as the
WebServer(IPlanet, Apache)

SSL with virtual hosting in Weblogic Server 5.1(WLS5.1)

Hello,
I am tasked with implementing a virtual hosting situation that must
use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
and https://www.ccc.com all having separate IPs. These URLs must
forward the request to the same WebLogic Server instance. The problem
is each URL must have its own certificate while WLS 5.1 only uses one
certificate per instance.
I was thinking about using a proxy server such that all three Web
servers that would host the URLs would be sent to a proxy server which
would redirect to the WLS 5.1 instance.
My questions are, would this be feasible using WLS 5.1 as the Web
Server and again WLS as the App Server? How secure is this
arrangement? Is it preferable to use another vendor's software as the
WebServer(IPlanet, Apache)

Hi Andy,
I think a good approach for you would be to use a proxy server --
browser -> proxy that supports virtual hosting -> WebLogic
Use a proxy which supports virtual hosting, and which can have a separate
certificate bound to each virtual host.
That way you can do SSL between the browser and the proxy, and you can
have the proxy do cleartext to WebLogic.
This situation gets around WebLogic's limitation of allowing only one
certificate per instance of the server.
You could also use 5.1 as the proxy in the following manner:
Run 3 instances of Weblogic, each as a proxy server, each bound to a
different IP address and DNS name, having its own certificate --
one instance for aaa.com, another for bbb.com, and a third for ccc.com
Then have each of these three instances of WebLogic proxy to your "app
server" instance of WebLogic on the backend.
Hope this makes sense.
Joe Jerry
Andy Walker wrote:
Hello,
I am tasked with implementing a virtual hosting situation that must
use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
and https://www.ccc.com all having separate IPs. These URLs must
forward the request to the same WebLogic Server instance. The problem
is each URL must have its own certificate while WLS 5.1 only uses one
certificate per instance.
I was thinking about using a proxy server such that all three Web
servers that would host the URLs would be sent to a proxy server which
would redirect to the WLS 5.1 instance.
My questions are, would this be feasible using WLS 5.1 as the Web
Server and again WLS as the App Server? How secure is this
arrangement? Is it preferable to use another vendor's software as the
WebServer(IPlanet, Apache)

Separate Wiki Data Stores for Virtual Hosts?

Is it possible to set different data stores to be used for the wikis associated with different sites (i.e. virtual hosts) on a Mac OS X Server (Snow Leopard)?
By default they are in "/Library/Collaboration/" and that is applied to ALL hosted sites.
My client would like a little more differentiation than that offered by user and/or group login.
Thanks in advance.
+*Geoff Heys*+

Ditto.
I noticed it when logged in as a user with permissions to a specific wiki on the server, and went to 'My Page', that updates from all the other wikis on the server are listed, in addition to the updates for the wiki I belong to. I can't get to them by clicking on the links, but they show up in the list. Makes it pretty hard to focus on your wiki, when you see updates from multiple other wikis listed.
It would seem like there must be a fix in the code for both the 'My Page' and the generic top-level '/groups', but I don't know the code structure well enough yet to figure out how/where to fix it.
Anyone else find a solution for this? I don't think I can roll out multiple domains/wikis on one server, if this behavior is present.

Jk_mod configuration in virtual host

Hi,
I met a strange problem.
Apache has several virtual hosts. Each virtual host has its own configuration file, which is "included" into main httpd.conf .
If I define JkMount directive in virtual host conf file inside <VirtualHost>, it does not work.
If I move it to the httpd.conf at the top level, it works fine.
Could you help me out to launch it on <VirtualHost> level.
Thanks.

Hi there,
I just wanted to clarify my question, has anyone been able to use group authentication using OID to restrict access to websites hosted using AS10g? My website is just plain html, but maybe someone has done something similar by adding a java wrapper to perform the authentication (that seems like overkill to me but maybe there is a more elegant workaround)?
Thanks,
Karen

DNS zones for Mail virtual host

Hello,
We have a split DNS server hosting mail for company.com. So we have a DNS zone called company.com with the appropriate records (A, MX).
We now need in the same box to host mail for another domain, company.org. Do we have to create a separate DNS zone for company.org with another A record for the server?
Regards
Kostas

If you're going strictly for mail and with no other network services are associated, then Camelot is quite correct and you can use an MX, and enable virtual hosting within the mail server.
If you're doing "other stuff" with that domain, then you'll need the zone.
Given the usual fondness for, well, "incomplete" questions and for server configurations and networks that, um, "evolve", then the answer I'd use is "yes"; add the zone. (If for no other reason than somebody's eventually going to want a web server with the domain, or...)
I'm not a big fan of split-horizon though I can and do use it for specific cases. I prefer to partition "inside" from "outside", and that avoids this quagmire.
And FWIW, "example.com", "example.org" and "example.net" are RFC-reserved domain names available for posting obfuscated examples and questions, for documentation, and related use. "company.com" and "company.org" are real and registered domains.

OAM Webgate installation on APache with multiple Virtual hosts?

Hi I have customer who is having One Single APache web server and having two different applications configured as different Virutal hosts in the single server.
requirement is , Each application should be protected by OAM Webgate and each application have seperate session configurations. So, How can we handle this ..
I am thinking to install webgate for each application virutal Host to fulfill this requirement but i am worrying about the Webgate installation since both applications on single Apache server and single httpd.conf file.
Really appreciated if anyone suggest me the approach of how to fulfil this requirement.
-Srini
Edited by: user567398 on Jun 17, 2011 3:00 PM

Hi Srini,
You can use a single WebGate - in the "Preferred HTTP Host" setting for the WebGate in the Access System Console, specify SERVER_NAME. OAM will then use the name of the Virtual Host (as returned by Apache) when evaluating policies, and you can have different policies by having different Host Identifiers for the two (or more) virtual hosts.
Regards,
Colin

Virtual host doesn't work in NW CE 7.1 EHP 1 SP07

Hi all,
I've created a virtual host in nwa using "Java HTTP Provider Configuration: Virtual Hosts"
(f.e. virtual host named "we2")
But I can't access to this using http://we2:50000. I don't know why.
DNS is up to date.
many thanks
Sven
Edited by: Sven Rickelt on Sep 20, 2011 3:16 PM

Hi,
Have you done configuration as per below link:
http://help.sap.com/SAPHELP_nwpi711/helpdata/en/f5/875342d8a7be30e10000000a155106/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/en/44/9a891684d360d6e10000000a114a6b/content.htm
Thanks
Sunny

PHP "Virtual Host" Site error Using Dreamweaver

I created a virtual host on my local machine. I am using Apache, php5, and mysql 5. I moved my "wordpress files and folders" into the root folder for my site. My htdocs looks like this;
<VirtualHost *:80>
ServerName localhost
DocumentRoot "C:/Program Files/Apache Group/Apache/htdocs"
</VirtualHost>
<VirtualHost *:80>
ServerName myvirtualrootfolder.com
DocumentRoot "C:/Program Files/Apache Group/Apache/htdocs/myvirtualrootfolder"
<Directory "C:/Program Files/Apache Group/Apache/htdocs/myvirtualrootfolder">
    Options FollowSymLinks Indexes
    Allow from all
    Order allow,deny
    AllowOverride All
</Directory>
</VirtualHost>
I followed the dynamic dreamweaver setup. Next I see, "This page may have dynamically-related files that can only be discovered by the server. When I click "Discover", I'm told "my site definition isn't correct." Can anyone help me please?

>Sorry. I just never get any help here
Really? Doesn't look that way to me:
http://forums.adobe.com/people/buffbill?view=overview
Other than a post from last week, and those you just posted within the past few hours....it looks like you are getting replies. I'm just sayin.

Use require group in virtual host

Hi,
I have set up several virtual hosts in my middle tier, and configured them as partner applications so that OID/SSO can be used for authentication. It works fine, but the only supported method I can see is 'require valid-user' which allows any user in OID access to all virtual hosts. Does anyone know of a way around this using OID (not mod_auth). We want to allow users within a group access to individual virtual hosts.
Thanks,
Karen

Hi there,
I just wanted to clarify my question, has anyone been able to use group authentication using OID to restrict access to websites hosted using AS10g? My website is just plain html, but maybe someone has done something similar by adding a java wrapper to perform the authentication (that seems like overkill to me but maybe there is a more elegant workaround)?
Thanks,
Karen

Using different DocumentRoot directive within virtual hosts

Similar Messages

Maybe you are looking for