First listed virtual host is masking others
I am running a couple of virtual hosts started through the standard Server Admin GUI. All vhosts are name-based. I have three:
default (no domain name, port 80)
site1 (site1.myschool.edu, port 80)
site2 (site2.myschool.edu, port 80)
they are listed in that order in the GUI, all are active, each has a separate access and error log and separate document roots.
Any request to either the naked IP address of the machine, or to the domain names for the second and third site are showing the content from the first default site. The log files for the second two are not being written to, and the index files for the second two are not showing. It appears that the first virtual host is masking the other two.
I've tried re-ordering to place the default last, but whatever I do, the first vhost listed masks the other two.
Any ideas what might be going wrong here? All the configuration was done through the Server Admin GUI, so I haven't been mucking about with the on-disk conf files in /etc/httpd
Thanks in advance for any ideas.
Cris
Check the aliases tab for each site and make sure none of the contain a *
The * says match all hostnames, so Apache won't bother looking for additional sites if it finds one.
Similar Messages
-
Hello,
I have a enabled http access to my G4 and also FTP. I now would like to host my other sites.
How can I enable virtual hosting?
I have looked at documentation relating to this but have come unstuck as I have tried to look for the areas in the httpd.conf file that controls this. I think I found it but I'm not at all unix or command-line savvy so I don't wish to stuff it up. I have also looked through Apaches' on line documentation but I cant find any straight forward "this is what to change and this is how to change it" document. There seems to be much to do through terminal in order to allow virtual hosts, and there is also security which I believe is contained in other apache files. The mac is standalone and I think I need to allow it to be inetd? Is that right?
Is there alternative software apart from apple server, that a novice like me can learn from or allow me to set these up through a gui?
Thanks for your helpHi--
sorry for the delay in responding have been away for
xmas, will ask for advice on the apache boards,
You can also ask for advice here. Unless the Apache boards have an area specifically for Apache on OS X, you could get confusing advice. Apple's Apache uses a different file layout than Linux, for example. Also, the Apache on OS X is still version 1.3, so you can get confusing advice there, too.
but I
will give nedit a go to see what it does.
If you find nedit too daunting to install (it requires X Windows, for example, so you'd need that), you should look at Bare Bones' TextWrangler (if you're not already using BBedit, that is). You can use it to open the Apache configuration files. There's even an Apache Configuration Language module that works with TextWrangler. To install it into TextWrangler, just substitute "TextWrangler" in the path given on the Daring Fireball page. It works like a champ with either BBEdit or TextWrangler.
Do you think it would be worth
investing in apple server?
If all you want to do is to set up virtual hosts on your computer, I don't think it's worth it. I haven't used the GUI tools for setting up so I don't know how good they are, though.
But it's pretty simple to set up a virtual host on regular OS X. Basically, you open up the Apache configuration file. If you're using TextWrangler, and you installed the command line tool, it's as easy as typing this in the Terminal application:
<pre class="command">edit /etc/httpd/httpd.conf</pre>TextWrangler will take care of the proper authentication when it comes time to make changes or save your file.
The first thing to look for in your httpd.conf file is the NameVirtualHost directive. By default, it's commented out (has a "#" in front of the line):
<pre class="command">#NameVirtualHost *:80</pre>Just remove the "#" from the front of the line.
Then, a little further down, there's an example host but it's commented out:
<pre class="command">#<VirtualHost *:80>
# ServerAdmin [email protected]
# DocumentRoot /www/docs/dummy-host.example.com
# ServerName dummy-host.example.com
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common
#</VirtualHost></pre>I always leave that alone, but start my virtual hosts just below that. It can be as simple as this:
<pre class="command"><VirtualHost *>
DocumentRoot "/Library/WebServer/sitedirectory"
ServerName www.domain.com
</VirtualHost></pre>You can, however, get fancy and add all kinds of directives into that block, customizing your virtual host as much as you want. My suggestion would be to try setting up a virtual host and see where you get stuck, then post back with questions.
As for messing up the httpd.conf file, don't worry about it too much. There's a "default" copy of the file in the /etc/httpd directory that you can always go back to. Or, do what I do before I'm about to try something that could turn ugly: make a copy of the current configuration file:
<pre class="command">sudo cp /etc/httpd/httpd.conf /etc/httpd/httpd.conf.cmbak.1</pre>Where I just incremement the "1" on the end. Or I put the date on there: httpd.conf.cmbak.20061229. That way, I always have the current file to fall back on...
And don't forget: any time you make a change to the httpd.conf file, you have to stop and restart the web server! That's so easy to forget. Also, if you're changing the configuration, these two Terminal commands will be your friends:
<pre class="command">/usr/sbin/apachectl configtest
/http -S</pre>
The first one tells you if you have any syntax errors in your configuration file, the second will tell you about your virtual host setup.
charlie -
Virtual hosts and mod_oc4j. Can someone from Oracle please answer, at least reply.
Can someone please explain how to configure mod_oc4j and virtual hosts. It can be done with mod_jk, but I am have major problems in getting it to work with mod_oc4j.
I am not sure about mod_jk so I won't touch that.
mod_oc4j introduces directives that have the scope of either default server or virtual host - just like most OHS (Apache) directives. By default, these directives are in a file mod_oc4j.conf, and this file is included at the highest level.
If you do want those mount points defined in mod_oc4j.conf to be available only to a certain virtual host etc., you can either create a mod_oc4j_vh1.conf file and have it included within the scope of the vh1 virtual host. Or, you can just define those directives right within the vh1 virtual host directive. -
Hi ,
R12.1.3 & 11gR2 DB
I have a qucik question . When We have Virtual Host Name for setting , What Should be the node name for ICM in Concurrent Manager Admin form.
In One of our Instance : For ICM & Other Manager , its Virtual Host Name
For Other : ICM : Physical Host Name & Other Manager Virtual Host Name .
Which is good. We having a issue with ICM on both Nodes , in every minutes is going down and come up automatically.
Regards
Sourabh GuptaHi Hussein,
Thanks a lot. I have already review these document.
Is Auto Failover With Virtual Hostnames For Concurrent Processing Servers Supported In 11i Or R12? (Doc ID 456540.1)
Adding an Alias Hostname with Oracle E-Business Suite Release 12 (Doc ID 603883.1)
Concurrent Processing - CONC-SM TNS FAIL In Internal Concurrent Manager (ICM) Log File With Virtual Hosts Configuration [ID 961216.1]
ICM Not Starting: Node Name not Registered [ID 602942.1]
I am curious what should be the node name in concurrent manager Administrator form.
W ether is should be the virtual host name or physical host name.
I have just checked with few people , Some Says ICM node name should be Physical server name & Other CM name can be Virtual name. I am not sure on what basis people are saying.
Few says node name should be the physical host for every CM.
Note Sure what is correct & best configuration.
Regards
Sourabh GUpta -
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. -
Wiki listed under other virtual hosts
I have a wiki where under "Settings > Advanced" it is set to be restricted to a specific hostname. Using http://www.myhost.com/groups/mywiki I can access the wiki fine, and I see it listed when I go to http://www.myhost.com/groups/. If I try to access the wiki using a different hostname (e.g. http://www.otherhost.com/groups/mywiki ), I get a 404 error (so far so good). However, if, using this other hostname, I ask for a list of available wikis (i.e. http://www.otherhost.com/groups/) the wiki is listed there, even if I get a 404 when I click on it. Shouldn't the wiki be invisible? How do I make it so that the wikis under one virtual host are completely isolated from other virtual hosts?
I have tried deleting and recreating the wiki; turning the Settings > Advanced on and off; etc etc. Same behavior each time.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. -
Corrupted wiki list with multiple virtual host
Hello,
I have several virtual hosts and I want each of them to only list of wikis which are associated with them using the Wiki Admin Settings -> Advanced : Specific Host Names.
This does not seem to work. As soon as a wiki is associated to a specific virtual host it disappears from the list of wiki (http://hostname/groups/) (on all virtual hosts actually). The wiki itself can still be accessed by its explicit address: http:/hostname/groups/wikiname
If I manually edit the sql3 file directoryIndex.db in /Library/Application Support/Apple/WikiServer
and replace the specific host name by "*", the wiki reappears in the wiki list but on ALL virtual host. Still it remains accessible only in the one designated in the wiki Settings.
Most frustrating. Any workaround ? Seems like a bug but the wiki implementation being so convoluted I am not completely sure.
Any help ?
Thanks
PaulHi,
Seems to work on my test ASA
Attached it to my current LAN interface.
ASA(config)# packet-tracer input LAN tcp 10.2.11.1 12345 64.156.192.154 80
Phase: 1
Type: ROUTE-LOOKUP
Subtype: input
Result: ALLOW
Config:
Additional Information:
in 0.0.0.0 0.0.0.0 WAN
Phase: 2
Type: ACCESS-LIST
Subtype: log
Result: ALLOW
Config:
access-group outbound_access in interface LAN
access-list outbound_access extended permit object-group obj_Meraki_outbound object-group obj_Meraki_lan object-group obj_Meraki_pub
object-group service obj_Meraki_outbound
service-object tcp destination eq https
service-object tcp destination eq www
service-object tcp destination eq 7734
service-object tcp destination eq 7752
service-object udp destination eq 7351
object-group network obj_Meraki_lan
network-object 10.2.11.0 255.255.255.240
network-object 10.5.11.0 255.255.255.240
object-group network obj_Meraki_pub
description: This group lists all hosts associated with Meraki.
network-object host 64.156.192.154
network-object host 64.62.142.12
network-object host 64.62.142.2
network-object host 74.50.51.16
network-object host 74.50.56.218
Additional Information:
access-list outbound_access line 1 extended permit tcp 10.2.11.0 255.255.255.240 host 64.156.192.154 eq www (hitcnt=1) 0x4d812691
Also have used such configuration in some special cases where the customer has insisted on allow specific TCP/UDP ports between multiple networks. And nothing is stopping from adding ICMP into the "object-group service" also.
- Jouni -
Baffled - "unknown virtual host" when creating new list
*I am getting this message:*
_Error: Unknown virtual host: mail.riverstoneschool.org_
*when I attempt to create a new list. What's baffling is that we don't have any virtual domains and the domain listed in the message is our primary domain. Here's the mm_config.py: (minus the initial comments)*
from Defaults import *
# Put YOUR site-specific settings below this line.
MTA = 'Postfix'
DEFAULTEMAILHOST = 'mail.riverstoneschool.org'
DEFAULTURLHOST = 'mail.riverstoneschool.org'
DEFAULTURLPATTERN = 'https://%s/mailman/'
IMAGE_LOGOS = '/images/'
DEFAULTADMIN_MEMBERCHUNKSIZE = 150
OWNERSCAN_DELETE_THEIR_OWNLISTS = yes
*In case it's relevant, here's the dig results for "mail.riverstoneschool.org" when run from the server in question (ie: from mail.~ itself). Also in case it's relevant, this Mac server is the one hosting DNS, too:*
rs-server-ws:Mailman matthewmiller$ dig mail.riverstoneschool.org
; <<>> DiG 9.4.3-P3 <<>> mail.riverstoneschool.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14059
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 2
;; QUESTION SECTION:
;mail.riverstoneschool.org. IN A
;; ANSWER SECTION:
mail.riverstoneschool.org. 14400 IN A 10.100.1.10
;; AUTHORITY SECTION:
riverstoneschool.org. 14400 IN NS mail2.riverstoneschool.org.
riverstoneschool.org. 14400 IN NS rs-server-ws.riverstoneibs.lan.
riverstoneschool.org. 14400 IN NS mail.riverstoneschool.org.
;; ADDITIONAL SECTION:
mail2.riverstoneschool.org. 14400 IN A 10.100.2.10
rs-server-ws.riverstoneibs.lan. 10800 IN A 10.100.1.10
;; Query time: 1 msec
;; SERVER: 10.100.1.10#53(10.100.1.10)
;; WHEN: Mon Oct 18 13:11:10 2010
;; MSG SIZE rcvd: 169
Thanks in advance for any assistance you can offer!
-MatthewHi Kevin,
I think you have to set the query specification for the data provider you created. If you don't, no object is available (that'w why you received a such error).
Best regards,
Anthony -
Virtual hosts in apache defaults to first host
On my MacMini I have set up apache to use virtual hosts I and use a mounted USB drive to host the sites (in my case /Volumes/Work1/www as root). I have configured 3 sites and switch on the subdomain (in my case and in order in the virtual hosts file: hbc1.helsted.net, consulting.helsted.net, store.helsted.net).
On the MacMini I have inserted the urls in the hosts file to point at localhost for two of the entries and all work beautifully on the MacMini for those two. Anywhere else (and from the MacMini on the one not in the hosts file) the system defaults to the first entry in the virtual hosts config file (as the documentation says it will if the url is not recognized) which is displayed in the browser and which has entries in the log file.
After some time the server occasionally refuses to serve the pages and I get a 403 error (access denied). Again not on the MacMini with the hosts file entries. Looking at the error log from apache in that case it appear that it has got the full url served as it is in the log file.
Restarting the web share removes the 403 error (until next time).
Any hints on how to to resolve my two issues?Thanks for the reply, my vhosts config file contains the following (note that the viewer in the forum browser removes the initial #es on the comment lines):
# Virtual Hosts
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
# Please see the documentation at
# <URL:<a class="jive-link-external-small" href="http://">http://httpd.apache.org/docs/2.2/vhosts/>
# for further details before you try to setup virtual hosts.
# You may use the command line option '-S' to verify your virtual host
# configuration.
# 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>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/hbc1"
ServerName hbc1.helsted.net
ErrorLog "/private/var/log/apache2/hbc1.helsted.net-error_log"
CustomLog "/private/var/log/apache2/hbc1.helsted.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/consulting"
ServerName consulting.helsted.net
ErrorLog "/private/var/log/apache2/consulting.helsted.net-error_log"
CustomLog "/private/var/log/apache2/consulting.helsted.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/store"
ServerName store.helsted.net
ErrorLog "/private/var/log/apache2/store.helsted.net-error_log"
CustomLog "/private/var/log/apache2/store.helsted.net-access_log" common
</VirtualHost>
<Directory /Volumes/Work1/www>
Options Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>
Message was edited by: skhelsted -
How to confiture virtual hosts with multiple domain names
hello,
I've read through some of the postings here on virtual hosts, but I thought I'd better solicit advice before I actually try some of the things I've read about.
In a nutshell, I've purchased multiple domain names that I'd like to alias to a new site (currently it is just a subfolder in the main site directory) on my OS 10.3.x server. There is only the one main site configured right now on the box, so I know I need to set up a second "virtual site" pointing to the files in this subfolder to make it function as its own site.
I've dabbled around with the sites settings in the GUI, but I'd probably be most comfortable setting all this up in the httpd.conf by hand if I could. But I'm weary of this because I know it might be better to use the GUI because of OS X Server's flavor of WebObjects and Apache (sigh).
So, I have two main questions:
1) How would I set up this second site using the GUI in server settings? Do I need to first move the subfolder out of the main folder before it can be designated its own site? Or can I just point to it in the GUI? Can I use one of my purchased domain names in the domain field?
2) Currently, I have URL Forwarding set with my multiple domain names, but I'm thinking there might be a better way to do this? For SEO I'd rather use some type of redirect rather than being penalized by search engines for having what looks to be multiple domains pointing to the same site.I'm thinking I should create virtual sites for each domain name I've purchased with a hard redirect back to the main site?
Any suggestions would be appreciated.
Thanks
G4 Mac OS X (10.3.9) 10.3.9 Server
G4 Mac OS X (10.3.9) 10.3.9 Serverthank you for your reply.
> You can create each site as a new Site in Server
Admin. When you do this you can choose any
directory on disk as the document root for each
site.This means you can move the sites' folders out of
/Library/WebServer/Documents if you like - you could
create /Library/WebServer/site1,
/Library/WebServer/site2, etc. (or even be outside of
/Library/WebServer if you want).
so, are you are saying that I could designate one site to be
/Library/WebServer/Documents/site1
and another to be
/Library/WebServer/Documents/site1/directory1
even though directory1 is contained within site1's structure? I'm not advancing this as a good idea, necessarily. I'm just wondering if Apache would complain.
> Each site should have the domain name set as per your
registered domains. Apache will need this to
determine the correct site to serve for each
request.
Well, after some additional research I'm thinking I'm missing a critical piece of the puzzle. That being access to the DNS host server that manages the context of my server. I have purchased domain names through an outside registrar that point to my site and I can create virtual hosts on my server, but I don't have the ability to add the new virtual host names into the DNS server that manages my box. If that makes sense. Or maybe I'm missing something?
>
I'm not sure why you're using URL forwarding at all.
Without that piece of information it's impossible to
tell you whether you should continue using them or
not - in general there's no need to use URL
forwarding if you have multiple Virtual Hosts setup,
but it sounds like you have multiple hostnames
pointing to the same content, so your needs may be
different.
I'm using forwarding for the reason I list above. I didn't purchase hosting with the registrar where I purchased my domain names, so they are parked on the registrar's name server with URL forwarding to my server. The DNS server that manages my box resides in a different location and I don't have the ability to add DNS entries pointing to virtual hosts that I want to set up. Am I stuck?
G4 Mac OS X (10.3.9) 10.3.9 Server -
AddNode cannot find Virtual Host name
Hi,all;
I want to replace a server in RAC for example RAC1. at first,I deleted node RAC1,this step is total clean out all information of RAC1 in the cluster.
then prepare new machine of RAC1 for cluster install.
When I run addNode.sh in RAC2 to re-add clusterware to RAC1. the first step of addNode is fill up the information of new node,Public node name,Private node name,Virtual host name.
It will list such info of the remain node also.
In my operation,It can find all info of new node which is rac2,rac2-priv,rac2-vip. but the remain node's Virtual host name is blank -- it shuould be rac1-vip.
In this step,I still click "Next" to proceed my operation and return not any error.
at the end of addNode.sh it will execute 3 script to end out operation of add clusterware to new node.
the third script is to run /opt/oracle/product/10.2.0/crs_1/root.sh in the new node RAC1,
the screen print "*Expecting the CRS daemons to be up within 600 seconds*."
but after waited more than *6000* seconds,it returned nothing to me,It seem idle! I cancle the script manual.the result is the CRS can not run on RAC1.
in RAC2,crs_stat -t can see ora.rac1.gsd , ora.rac1.ons , ora.rac1.vip. but they are all offline.
and run vipca in RAC2 reture
ora.rac1.gsd has placement error
ora.rac1.ons has placement error
has not more detail log file left in server.
I think all of my operation is normal and In line with the rules except it cannot export remain node's Virtual host name.
How to fix it? any ideal?
thank you.[oracle@RAC1 ~]$ cluvfy stage -pre crsinst -n rac1
Performing pre-checks for cluster services setup
Checking node reachability...
Node reachability check passed from node "RAC1".
Checking user equivalence...
User equivalence check passed for user "oracle".
Checking administrative privileges...
User existence check passed for "oracle".
Group existence check passed for "oinstall".
Membership check for user "oracle" in group "oinstall" [as Primary] passed.
Administrative privileges check passed.
Checking node connectivity...
Node connectivity check passed for subnet "192.168.1.0" with node(s) rac1.
Node connectivity check passed for subnet "10.10.10.0" with node(s) rac1.
Suitable interfaces for the private interconnect on subnet "192.168.1.0":
rac1 eth0:192.168.1.100
Suitable interfaces for the private interconnect on subnet "10.10.10.0":
rac1 eth1:10.10.10.1
ERROR:
Could not find a suitable set of interfaces for VIPs.
Node connectivity check failed.
Checking system requirements for 'crs'...
Total memory check passed.
Free disk space check passed.
Swap space check passed.
System architecture check passed.
Kernel version check passed.
Package existence check passed for "binutils-2.15.92.0.2-13".
Group existence check passed for "dba".
Group existence check passed for "oinstall".
User existence check passed for "nobody".
System requirement passed for 'crs'
Pre-check for cluster services setup was unsuccessful on all the nodes. -
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/*" -
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
-johnBecause 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 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 AroraFollowing 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 -
Hi,
I have removed a successfully installed Grid Infrastructure Software. Now I was again installing it but the Installer is complaining about "[INS-40912] Virtual host name assigned to another system on the network", which it was not complaining about in the first installation process. :/
EDIT: I have checked and the two cluster-nodes are interpingable through their virtual IP's.
I see that the previous installation has created an own interface for that virtual IP:
eth0:2
Link encap:Ethernet HWaddr 00:50:56:B9:0E:AA
inet addr:10.200.11.159 Bcast:10.200.11.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19 Base address:0x2000OK Solved: I just did:
ifconfig eth0:2 down
Maybe you are looking for
-
My iPad won't let me stay on some games and web sites for more than a few minutes . It closes the site and takes me back to home screen. Why and how do I fix this?
-
Site too small on New Palm Pre and Blackberry Pearl
I have a site that is pretty simple. It contains no tables accept for forms and input buttons. And isn't overloaded with CSS. It was orginally designed for keypad devices and has a width of 176px. Everything is spaced by either <p> or <br> tags with
-
Waring messages for PO Date in the contract creation?
Hi Friends, Expecting answers with some functional knowledge, I am developing one webservice to create value contract from dotnet front end, So user can enter inputs from that front end and he will get SAP generated value contract id. Here I did vali
-
Mouse over to change cell color
Can anyone point me to a really good tutorial for doing mouse over also changes the cell color?. Ive tried a few and spent hours on it and just cannot get it to work correctly. Here is my basic starting .css which i start off with each time. .tnav {
-
Why are my App Tabs not sticking w/ FF4.0?
Just downloaded FF4.0 and love the App Tab feature. However, unlike the demo video, my App Tabs don't automatically reload when I exit and restart FF. I checked the browser options and nothing addresses this.