httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Barrett" <jnjbarr...@charter.net>
Subject Re: [users@httpd] Newbie question
Date Wed, 26 Mar 2003 15:49:13 GMT
oooooooooh ok it all makes sense now.  First off I thought I heard serving 2
web sites on 1 ip was impossible, but now I see it is.  Now it makes sense.
Ok thanks :D


----- Original Message -----
From: "Boyle Owen" <Owen.Boyle@swx.com>
To: <users@httpd.apache.org>
Sent: Wednesday, March 26, 2003 5:47 AM
Subject: RE: [users@httpd] Newbie question


> >-----Original Message-----
> >From: Joe Barrett [mailto:jnjbarrett@charter.net]
> >
> >  First I'm not a newbie to apache servers, just the vocabulary.  I'm
> >thinking of registering a www.whatever.com, and if I do, would
> >I put that name under the domain thing in my httpd file?
> >What does
> >domain mean?  Why would my computer need to know that? Doesn't my
> computer just
> >need my IP address, and somewhere on the web the big list of website
> >"domains" and IP's are kept?
>
> What "domain thing"? There is no apache directive called "DomainThing"
> but, as you're not an apache newbie, you probably know that :-)
>
> A name like www.acme.com is called a "Fully-Qualified Domain Name"
> (FQDN) and this is a human-readable string which represents the IP
> address of a server on the internet.
>
> The way it works is this:
>
> - your apache server "Listens" to an IP address. How you get the machine
> to respond to an IP address is a TCP/IP issue (not apache's problem). I
> assume you have set up your network card to respond to an IP. So now
> apache Listens to any HTTP requests on port 80 at that IP address.
>
> - the client types your FQDN into the browser. The browser asks its OS
> for an IP address for that FQDN. This is called Domain Name Resolution
> and may involve the client machine querying name servers on the internet
> (this is the "big list of domains" you mentioned - although really its a
> distributed database).
>
> - once it gets the IP, the browser sends an HTTP request to that IP
> address using TCP/IP. If you only have one site, then, yes; the server
> doesn't need to know its own domain name. So if you are www.acme.com and
> your IP address is 192.168.1.1 then the URLs http://www.acme.com/ and
> http://192.168.1.1/ will both lead to your site.
>
> Having said that, it's a good idea to include your FQDN in the
> ServerName directive since it allows apache to use the FQDN when it
> makes redirect URLs for the client. Otherwise, your client's browser
> might end up displaying your IP address which is a bit messy.
>
> - If, however, you have more than one FQDN sharing the same IP address,
> then the client *must* include the FQDN in the request. It places it in
> "Host:" header of the request and uses HTTP/1.1.
>
> - when such a request arrives at your server, apache reads the Host
> header and serves the request from whichever name-based virtual host has
> a ServerName which matches the Host, e.g.
>
> NameVirtualHost 192.168.1.1
>
> <VirtualHost 192.168.1.1>
>   ServerName www.acme.com
>   DocumentRoot /path/to/acme
> ...
> <VirtualHost 192.168.1.1>
>   ServerName www.bdnf.com
>   DocumentRoot /path/to/bdnf
> ...
>
> Check the docs for these directives for more details.
>
> Rgds,
> Owen Boyle
> Disclaimer: Any disclaimer attached to this message may be ignored.
>
> >
> >
> >---------------------------------------------------------------------
> >The official User-To-User support forum of the Apache HTTP
> >Server Project.
> >See <URL:http://httpd.apache.org/userslist.html> for more info.
> >To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> >   "   from the digest: users-digest-unsubscribe@httpd.apache.org
> >For additional commands, e-mail: users-help@httpd.apache.org
> >
> >
>
> This message is for the named person's use only. It may contain
> confidential, proprietary or legally privileged information. No
> confidentiality or privilege is waived or lost by any mistransmission.
> If you receive this message in error, please notify the sender urgently
> and then immediately delete the message and any copies of it from your
> system. Please also immediately destroy any hardcopies of the message.
> You must not, directly or indirectly, use, disclose, distribute, print,
> or copy any part of this message if you are not the intended recipient.
> The sender's company reserves the right to monitor all e-mail
> communications through their networks. Any views expressed in this
> message are those of the individual sender, except where the message
> states otherwise and the sender is authorised to state them to be the
> views of the sender's company.
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message