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.

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

Http deny and virtual hosts

solaris 8 ips sp4 gw and server on 1 host
got 5 domains en added these to the platform.conf
and using ssl cert to access these domains.
everything works fine but when i add the url the user
can access only in the domain policy url list and deny the rest i get a 502 gateway error ! log gateway says
sessionid not allowed ! what's wrong ?
adding http://domain.sub.com in allow list doesn't help

Hi,
Is there a "*" in the deny URL list. Looks like portal gateway checks deny list and denys all the URL's
without even the virtual host. Please try removeing "*" from the deny list.
Hope this helps.
Regards,
Raj_indts
Developer Technical Support
Sun Microsystems http://www.sun.com/developers/support

Http tunnelling not working with virtual host

Hi,
We have recently migrated our application from OC4J server to the Weblogic 11g server. There is one EJB client module which connects using t3 protocol. We are trying to use Http Tunneling for it. The server setup consists of two machines (machine1.global.com and machine2.global.com) in clustered mode. A virtual host cbs.global.com is configured to load balance across the above 2 two machine. Also Apache HTTP Server plugin is used for handling the web tier.
For enabling tunneling, we have checked the 'Enable HTTP Tunneling' check box in the server. Also in the Httpd.conf file, we have added a block for
<Location /HTTPClnt>
SetHandler weblogic-handler
</Location>
If we give the initial context url as http://machine1.global.com:7005 or http://machine2.global.com, then it is working fine. But when we give the virtual host names - http://cbs.global.com or http://cbs.global.com:7005, it is not working. This application needs to be accessed outside the company network, so we cannot directly give the machine names and have to make it work using virtual host.
Please advise whether any other settings need to be done for enabling the tunnelling for virtual hosts.
Highly appreciate your help in this regard.
Best Regards,
Jaison
Edited by: user13152776 on Aug 29, 2011 7:00 PM

Thanks Peter for the reply.
We are having multiple managed servers configured to multiple ports - 7003, 7005, 7007, etc. Please find below the mod_wl_ohs.conf file
# NOTE : This is a template to configure mod_weblogic.
LoadModule weblogic_module "${ORACLE_HOME}/ohs/modules/mod_wl_ohs.so"
# This empty block is needed to save mod_wl related configuration from EM to this file when changes are made at the Base Virtual Host Level
<IfModule weblogic_module>
# WebLogicHost <WEBLOGIC_HOST>
# WebLogicPort <WEBLOGIC_PORT>
# Debug ON
# WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/weblogic.log
# MatchExpression *.jsp
# Dev Cluster Configuration - Port 7003
<Location />
SetHandler weblogic-handler
WebLogicCluster nooslux050d.gl.2wglobal.com:7003,nooslux051d.gl.2wglobal.com:7003
Debug ON
WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/devcluster.log
MatchExpression *
</Location>
<Location /intApp>
SetHandler weblogic-handler
WebLogicCluster nooslux050d.gl.2wglobal.com:7003,nooslux051d.gl.2wglobal.com:7003
Debug ON
WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/devcluster.log
MatchExpression *
</Location>
# Ocean Cluster Configuration - Port 7005
<Location /CQS>
SetHandler weblogic-handler
WebLogicCluster nooslux050d.gl.2wglobal.com:7005,nooslux051d.gl.2wglobal.com:7005
Debug ON
WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/oceancluster.log
MatchExpression *
</Location>
# Websi Cluster Configuration - Port 7007
<Location /si>
SetHandler weblogic-handler
WebLogicCluster nooslux050d.gl.2wglobal.com:7007,nooslux051d.gl.2wglobal.com:7007
Debug ON
WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/websicluster.log
MatchExpression *
</Location>
</IfModule>
Best Regards,
Jaison

Oracle application server 10g http server virtual host

Hi,
I have defined a new virtual host, changed its setting and create a folder with html file for redirection.
Now when i am trying to access that new virtual host it is redirecting me to the old application.
e.g.
old.domain.com taking me old application.
new.domain.com taking me old application.
in HTML file i wrote url like ... http://myappsserver:port .......
could you please tell me am i missing some thing..
thanks

You can find the port usage by executing opmnctl status -l from the command line. This should give you the port usage for each opmn-governed component. In a standard setup, web cache normally runs on port 7777 while Oracle HTTP Server runs on 7778. Alternatively, you can check the httpd.conf for the parameter Listen. This will give you the Oracle HTTP Server port as well.
Did you test with the directive NameVirtualHost added?

Ias console - HTTP Server - Virtual Host Error

Http server is working, but when clicked on the virtual hosts or server settings, mime settings.. the console shows this error.
An error was encountered trying to retrieve configuration data.
Failed to initialize configuration parameter ApacheMainServer.. Entity not found. Resolution: Entity not found Base Exception: The document returned by plugin "apache" is null, or does not have a root element, or does not properly formatted. Resolution: Check to see if the document is properly constructed. A document should not be null and should contain at least one root element.. Base Exception: The document returned by plugin "apache" is null, or does not have a root element, or does not properly formatted. Resolution: Check to see if the document is properly constructed. A document should not be null and should contain at least one root element.
ANYONE HAVE ANY INFO REGARDING THIS ?

You can find the port usage by executing opmnctl status -l from the command line. This should give you the port usage for each opmn-governed component. In a standard setup, web cache normally runs on port 7777 while Oracle HTTP Server runs on 7778. Alternatively, you can check the httpd.conf for the parameter Listen. This will give you the Oracle HTTP Server port as well.
Did you test with the directive NameVirtualHost added?

Problem with DNS and/or Virtual Host (works from inside, not from outside)

I am running several web sites (as virtual hosts) successfully on one Xserve (192.168.200), which are accessible internally and from the Internet (via forwarding port 80 on our firewall).
Now I am trying to add another web site (newmini.domain.com), which however is running on a Mac mini (also on the same subnet as the Xserve) at 192.168.100. What I did is make an additional entry under the Xserve's DNS for the domain (domain.com) (+ Machine..., pointing to 192.168.0.100). (I also made the necessary changes to the Mac mini's httpd and hosts configuration--no problem there).
Now, here's the strange thing: All computers on the subnet, whose DNS points to the Xserve, can see and browse newmini.domain.com fine. No problem. The computers ask the Xserve for the IP of the host in question, the Xserve says, "192.168.100", the request goes to the Mac mini, and it serves the web site as expected.
But this doesn't happen if the request comes from the Internet. Instead of seeing the Mac mini, the client sees the default web site of the Xserve... So it appears that somewhere, the virtual host part of the HTTP request is lost between our firewall and the Xserve.
Any ideas? Thanks.

It's not going to.
You say you've setup port forwarding on the firewall. Port forwarding only cares about the port number (80). It knows nothing about the nature of the request (e.g. the hostname that the web request is for). Therefore all extenal connections on port 80 get sent to the XServe. The newmini doesn't see the traffic at all.
If you only have a single public IP address you can only forward port 80 traffic to a single machine. Your options are to either use a different port number, or configure the XServe to proxy the connection to the mini (so now the traffic goes router -> XServe -> Mini -> XServe -> router), although that might not do what you want since it still places load and dependencies on the XServe.

How to create and access a Virtual Host on the J2EE WAS?

Hello, I have searched through the Forums and help.sap.com and found a lot of information on how to set up a Virtual Host on the J2EE server but am having issues with it working.
The goal is to provide a simple virtual host on the J2EE Portal server to host some static image and HTML files. Previously I had stored these files in the standard publicly accessible SAP J2EE folder location /usr/sap/<SID>/JCxx/j2ee/cluster/serverx/apps/sap.com/com.sap.engine.docs.examples/servlet_jsp/_default/root/. This location is resolved to when using the URL <host>:50000 for example.
The main issue here is that during Portal support pack applications this folder gets wiped out and we have to remember to save off any custom files and folders in this location and replace them.
I would like to create a virtual host to store these static files (i.e., branding-image.jpg, etc...).
I have run through the process of creating the virtual host both using Visual Administrator and <host>:50000/nwa but am not able to get the virtual host name to resolve properly.
The following are the steps that I have taken. Let's assume the standard SAP portal (i.e., xSS, etc...) is running properly on <host>:50000.
1. create virtual host via Visual Administrator/NWA called 'sapwebserver1' by using the Create Host option (takes on the attributes of the 'default' standard virtual host)
2. change the root directory for this virtual server to a custom folder at E:/tmp/mimes (where E:/usr is where the J2EE files are all installed), no start files were set up and nothing else was changed in the new virtual host record, no permissions were changed on the /tmp/mimes folder from whatever the default Windows user permissions are normally set, I am using a local Windows administrator account but I have not seen any reference in the help files or the examples that indicate that any specific permissions updates need to be made on the virtual host root folder
3. restarted the J2EE server as well as the HTTP Provider service
4. before updating the company DNS, I wanted to test this locally on the server and so have updated the server's local HOSTS file with a <host IP address> sapwebserver1 entry
5. from that server I can ping the sapwebserver1 virtual host name and it resolves properly to the machine's physical IP address
According to all of the documentation and examples I have seen I should now be able to (from that server) launch a browser and access the static files in the virtual host by referring to http://sapwebserver1:50000/branding-image.jpg for example. This is not working and the browser just brings up a Cannot display the web page error in IE. By referring to the virtual host name sapwebserver1:50000 it's supposed to hit the J2EE server and based on the host name sapwebserver1 realize that it should resolve to the root directory E:/tmp/mimes. This is not happening. Just as a test I have created a copy of the 'default' virtual host and called it sapwebserver2, updated the local HOSTS file for this entry, and tried to see if that would work like the 'default' host. My expectation was that http://sapwebserver2:50000 would behave the same was as http://<host>:50000 but it too fails to resolve just like the sapwebserver1 virtual host refernce.
Would anyone happen to have any pointers on what to do next? I just want a simple virtual host to be able to serve up some static images and files.
Thanks for any insight or assistance you might be able to provide here.
Graham

This defeats the purpose of trying to centralize SAP-related web resources on the SAP server. Typically IIS/Apache or other non-SAP servers are under the control of IT and not the SAP BASIS group.
We simply would like to have a centralized location to store static web files so that they are not overwritten during Portal support pack applications.

How can I connect to multiple WLS instances from a single Apache virtual host

Configuration : WebLogic 5.1 SP8 & Apache
I need to be able to have a configuration that looks something like this.
www.company.com/x -> WL cluster01
www.company.com/y -> WL cluster02
In all the examples that I have been able to find they alway defines the the WL
connection for the entire virtual host, but I need to be able to do it on a location
basis is that possible?
Thanks
Jens Schutt

httpd.conf:
<VirtualHost 172.17.9.24:443>
DocumentRoot "/www/X"
ServerName qawebivesta.qa.livecapital.com
ErrorLog /usr/local/apache/logs/qaweb1.error_log
TransferLog /usr/local/apache/logs/qaweb1.access_log
SSLEngine on
SSLCipherSuite
ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt
SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server.key
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
SSLOptions +StdEnvVars
</Files>
<Directory "/usr/local/apache/cgi-bin">
SSLOptions +StdEnvVars
</Directory>
SetEnvIf User-Agent ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
Debug ON
DebugConfigInfo ON
<Location /ivesta/>
SetHandler weblogic-handler
WebLogicHost qawlgc1
WebLogicPort 7001
</Location>
<Location /TMPPhase2>
SetHandler weblogic-handler
WebLogicHost qawlgc1
WebLogicPort 11001
</Location>
</VirtualHost>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/TMPPhase2 works fine, but when I try to access /ivesta I get a 404 from WebLogic
"https://qawebtmp.qa.livecapital.com/ivesta/index.jsp?__WebLogicBridgeConfig
Weblogic Apache Bridge Configuration parameters:
     WebLogic Cluster List:
          General Server List:
               Host: 'qawlgc1' Port: 11001
          DefaultFileName: ''
          PathTrim: ''
          PathPrepend: ''
          ConnectTimeoutSecs: '10'
          ConnectRetrySecs: '2'
          HungServerRecoverSecs: '300'
          MaxPostSize: '-1'
          DynamicServerList: ON
          StatPath: false
          CookieName: WebLogicSession
          Idempotent: ON
          FileCaching: ON
          DisableCookie2Server: OFF
          QueryFromRequest: OFF
          Build date/time: Jun 25 2001 15:09:34
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This should have been connecting to my 7001 instance not the 11001.
Thanks
Jens
"Eric Gross" <[email protected]> wrote:
What do you mean the wrong port? Post the complete output from
WebLogicBridgeConfig as well as the URL you used.
Also, paste the weblogic relative portions from your httpd.conf
Thanks,
Eric
"jens" <[email protected]> wrote in message
news:[email protected]...
I also used ?__WebLogicBridgeConfig to verify that it did pick up thewrong port.
Here is my build date for mod_wl.so in SP10
Build date/time: Jun 25 2001 15:09:34
Thanks
Jens
"Eric Gross" <[email protected]> wrote:
Make sure you are using the latest plugin. As well, add parameter:
DebugConfigInfo=ON and make a request with a query paramater of
?__WebLogicBridgeConfig and you should then see the build date/time.
We can
then see if you are indeed using the latest plugin.
It is not a possibility to get the source.
Regards,
Eric
"jens" <[email protected]> wrote in message
news:[email protected]...
And the solution where you put the WebLogic parm under location
the
last
location
over rule the previous.
I have also tried to upgrade my plug-in from SP8 to SP10 but that
didn't
make
any difference either.
Is it possible to get the source code for the plug-in, I'm afraid
that
it
don't
follow put's all it's parm's a the vhost level no matter where in
the
conf
file
they are placed.
HELP
Jens
"Eric Gross" <[email protected]> wrote:
Yu is correct.
Here is another way to do it as well:
MatchExpression /x
WebLogicCluster=server1:port,server2:port|PathTrim=/x
MatchExpression /yWebLogicCluster=server3:port,server4:port|PathTrim=/y
The general syntax for this would be:
MatchExpression exp name=value|name=value
Where exp=Mime type(*.jsp) or exp=/x(path)
The next argument in the list is a pipe(|) delimited list ofname=value
pairs (ie: WebLogicHost, WebLogicPort, WebLogicCluster, PathTrim,
PathPrepend, etc..).
Hope this helps.
Regards,
Eric
"Yu Tian" <[email protected]> wrote in message
news:[email protected]...
Hi Jens,
I think you can proxy by ppath.
<Location /x>
SetHandler weblogic-handler
WebLogicCluster cluster1
</Location>
<Location /y>
SetHandler weblogic-handler
WebLogicCluster cluster2
</Location>
thanks
Yu
"Jens" <[email protected]> wrote in message
news:[email protected]...
Configuration : WebLogic 5.1 SP8 & Apache
I need to be able to have a configuration that looks something
like
this.
www.company.com/x -> WL cluster01
www.company.com/y -> WL cluster02
In all the examples that I have been able to find they alway
defines
the
the WL
connection for the entire virtual host, but I need to be able
to
do it
on
a location
basis is that possible?
Thanks
Jens Schutt

ICal Error: "No virtual host found for iCal Service" - Help!

Trying to set up iCal on OS X Server 10.5.6
Server is up and running and successfully providing web services on its FQDN. Server is not currently used to support network users / services, but as and when it does it will be the Master Opendirectory server.
I have created a couple of test accounts on the server (simply in the Users group) and enabled both for Calendar Access.
I have provided the details of the FQDN on the iCal page, and checked that the default port (8008) has been opened in the firewall.
In web services there is one virtual domain (using name based virtual server) and the default domain in operation. Both appear to be functioning as would be expected.
When I click on 'start service' for iCal, I get this error.
"No virtual host found for iCal service"
I cannot find any information about this in iCal manual, or online documentation. Can anyone here provide pointer to where this information is, or what it means?
Would be most grateful.

Hey there,
See if any of the solutions provided in either of these older threads can steer you in the right direction.
http://discussions.apple.com/thread.jspa?threadID=1201737
http://discussions.apple.com/thread.jspa?threadID=1242823&start=0&tstart=-3
B-rock

[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)

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 define a separate virtual host for each client in SICF

Hello,
We have an ERP system with multiple clients running on it. The WebDynpro ABAP applications once developed are available on all clients, as standard. However, this is not our desired behavior. We want:
1. The WebDynpro ABAP applications should be managed separately in SICF depending on the client
2. The URL for accessing the WebDynpro application should have a own host name for each client. e.g.
A WebDynpro application on client 100 should be accessed by http://host1:5000/sap/bc/... and the same application on client 200 should be accessed by http://host2:5000/sap/bc/...
After a while researching I find out that creating a virtual host for each client in SICF would be a possible solution to fulfill the above mentioned requirments:
1. Set the profile parameter is/HTTP/virt_host_* with corresponding host name and port number
2. Create a new virtual host in SICF assigning the profile paramter to it
3. Assign a client to this virtual host
My question is how to specify a client to a virtual host? I didn't find any possibilities in SICF!
Anyone can help me? Thanks a lot in advance!
Best Regards
Di Li

Hi Srikishan,
thanks for your reply. Your suggested way is certainly a potential, and also my preferred option for solving the multiple-client-capable URL access to WebDynpro / BSP applications.
However, for some reasons, based on the customer requirements, the client should not be visible in the URL. The URL for accessing the WebDynpro / BSP applications on different client should have different host name, as if they are different companies. Besides that, we want to manage each WebDynpro / BSP application on different clients in SICF separately.
Therefore, at least on my opinion, we need to introduce a virtual host for each client in SICF. But how do I make it happen?
Regards
Di

How to define a separate virtual host for each client in ICF for WebDynpro

Hi,
We have an ERP system with multiple clients running on it. The WebDynpro ABAP applications once developed are available on all clients, as standard. However, this is not our desired behavior. We want:
1. The WebDynpro ABAP applications should be managed separately in SICF depending on the client
2. The URL for accessing the WebDynpro application should have a own host name for each client. e.g.
A WebDynpro application on client 100 should be accessed by http://host1:5000/sap/bc/... and the same application on client 200 should be accessed by http://host2:5000/sap/bc/...
After a while researching I find out that creating a virtual host for each client in SICF would be a possible solution to fulfill the above mentioned requirments:
1. Set the profile parameter is/HTTP/virt_host_* with corresponding host name and port number
2. Create a new virtual host in SICF assigning the profile paramter to it
3. Assign a client to this virtual host
My question is how to specify a client to a virtual host? I didn't find any possibilities in SICF!
Anyone can help me? Thanks a lot in advance!
Best Regards
Di Li

Hi Srikishan,
thanks for your reply. Your suggested way is certainly a potential, and also my preferred option for solving the multiple-client-capable URL access to WebDynpro / BSP applications.
However, for some reasons, based on the customer requirements, the client should not be visible in the URL. The URL for accessing the WebDynpro / BSP applications on different client should have different host name, as if they are different companies. Besides that, we want to manage each WebDynpro / BSP application on different clients in SICF separately.
Therefore, at least on my opinion, we need to introduce a virtual host for each client in SICF. But how do I make it happen?
Regards
Di

Problem Changing the Root Directory of the Default Virtual Host in J2EE 7.0

Hi,
I'm trying to change the root directory for the default virtual host in J2EE 7.0.
i did the following steps in visual admin: services -> HTTP Provider -> Runtime -> Virtual Hosts -> default:
Root Directory: "D:/usr/sap/<server>/<instance>/j2ee/cluster/server0/apps/sap.com/crm~b2b/servlet_jsp/b2b/root/b2b" (this the correct path to the application)
Start Page:"z_index.jsp"
I restarted HTTP Provider Service and the J2EE.
When I start http://<server>:<port> i get the following error:
The requested resource /z_index.jsp is not available
Details: File [z_index.jsp] not found in application root of alias [/] of J2EE application [sap.com/com.sap.engine.docs.examples].
sap.com/com.sap.engine.docs.examples is the initial default root directory, but i changed it to the correcht path...
Can anybody help me?
Yours
Michael
Message was edited by:
Michael Cendon

Hi,
hqt200475 wrote:
Hi,
I have the Environemt:
+ Linux SUSE 11 + Oracle Enterprise 11.2.0.2
oracle@stb:~> uname -a
Linux stb 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/LinuxMy Problem is changing the home directory of an existing Standalone-ASM:
/u00/app/oracle/product/11.2.0/grid_1/I want to move it to
/u00/app/grid/product/11.2.0/grid_1/My Question: what is the optimal path?
Optimal Flexible Architecture standard
All Oracle components on the installation media are compliant with Optimal Flexible Architecture. This means, Oracle Universal Installer places Oracle Database components in directory locations, assigning the default permissions that follow Optimal Flexible Architecture guidelines.
Oracle recommends that you use Optimal Flexible Architecture, specially if the database will grow in size, or if you plan to have multiple databases.
/u00/app/oracle/product/11.2.0/grid_1 - Oracle home directory for Oracle Grid Infrastructure 11g for a standalone server, if user owner of installation is "oracle"
/u00/app/grid/product/11.2.0/grid_1 - Oracle home directory for Oracle Grid Infrastructure 11g for a standalone server, if user owner of installation is "grid"
http://download.oracle.com/docs/cd/E11882_01/install.112/e16763/appendix_ofa.htm
Hope this helps,
Levi Pereira

Virtual hosts/HTTPS

Similar Messages

Maybe you are looking for