httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Klama" <nosed...@tampabay.rr.com>
Subject RE: [users@httpd] Beginner How-To
Date Thu, 05 Dec 2002 13:05:17 GMT
So would a request that is coming into the server go through a SSL
program that is on the server before it is passed to the Apache program
or is this something that can be configured as part of Apache?
Mike

-----Original Message-----
From: Justin Williams [mailto:justin@naturalwebs.com] 
Sent: Thursday, December 05, 2002 2:39 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Beginner How-To

SSL = Secure Socket Layer.  Provides encryption for information
travelling 
across the Web.  Usually, you'll want it when you are showing or
accepting 
sensitive information (credit cards, order information, personal
information, 
etc).

On Thursday 05 December 2002 12:37 pm, Michael Klama wrote:
> Thank you Justin.  I will have to do some research on SSL because I do
> not have a clue what that is.
>
> Mike
>
> -----Original Message-----
> From: Justin Williams [mailto:justin@naturalwebs.com]
> Sent: Thursday, December 05, 2002 2:30 AM
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Beginner How-To
>
> Most commonly, you will need a separate static IP for each domain you
> want to
> put an SSL on.  So, if you have 20 domains with no SSL and one domain
> with
> it, then you'll need 2 static IPs.  One can handle all of the domains
> with no
> SSL of their own; the other can handle the one domain with its SSL.
>
> On Thursday 05 December 2002 12:20 pm, Michael Klama wrote:
> > I do have one other question for now.  At what point do I need more
>
> than
>
> > one static IP address?
> >
> > MIke
> >
> >
> > -----Original Message-----
> > From: Justin Williams [mailto:justin@naturalwebs.com]
> > Sent: Wednesday, December 04, 2002 3:22 PM
> > To: users@httpd.apache.org
> > Subject: Re: [users@httpd] Beginner How-To
> >
> > Here's the scoop on DNS, in a very small nutshell:
> >
> > Remember old television?  The Adams Family?  Remember their address?
> > Bear
> > with me here..  this is old stuff...  They lived at 1313 Mockingbird
> > Lane.
> > So, keep that relationship in mind: Adams Family's House = 1313
> > Mockingbird
> > Lane.  Now Gomez and Thing most assuredly did not share teh same
> > residence in
> > that house, right?  Thing crashed in a cigar box...
> >
> > So, Consider Lurch to be your web server, Apache.  Apache keeps
track
>
> of
>
> > where
> > Gomez and Thing both live.  Seperate rooms.  If a visitor comes to
the
> > house
> > to visit Gomez, Lurch took the visitor to the library, or torture
>
> room,
>
> > or
> > wherever Gomez was.  If that visitor wanted to see Thing, Lurch too
>
> them
>
> > to
> > smoke a cigar...
> >
> > With me so far?
> >
> > So Lurch = Apache
> > Gomez = Web 1.
> > Thing = Web 2.
> > 1313 Mockingbird Lane = IP Address of both websites.
> >
> > Now, think about small towns in America.  Almost invariably, there
is
> > one old
> > busybody who knows everything about everybody.  That busybody is the
> > DNS.  A
> > visitor to the town asks that busybody where Gomez Adams lives, and
>
> gets
>
> > pointed to 1313 Mockingbird Lane.
> >
> > Likewise, a packet on the net looking for web 1, gets pointed by the
>
> DNS
>
> > to
> > the IP address.
> > Apache (Lurch) resides on that IP address, as well, and, when that
> > packet
> > arrives looking for Gomez, Lurch (Apache) takes him to the right
room
> > (the
> > directory where Web 1 is housed).
> >
> > For the record, yes, this is exactly how I describe the process in
my
> > Web
> > Design and Management class...  ;-)
> >
> > On Thursday 05 December 2002 01:13 am, Michael Klama wrote:
> > > This server will be in house and I plan on getting a static IP but
>
> was
>
> > > unsure if it was necessary.  Ideally I plan on having a web
hosting
> > > service that I run and am in the process of changing the 4 sites I
> > > currently have under contract from a hosting service to my own
>
> server.
>
> > > I have not had to think about all of the necessary components
> > > previously.  For the time being I can use the same Linux server
for
> >
> > DNS
> >
> > > and for the web server but once it is set up I will start
>
> advertising
>
> > it
> >
> > > and hopefully will soon need more equipment to cover both DNS and
> > > hosting.  My question after being so long winded is about the IP
> >
> > address
> >
> > > of the machine.  I assume (and correct me if I am wrong) that I
need
>
> a
>
> > > static IP for the DNS and the DNS will then distribute incoming
> >
> > requests
> >
> > > to the proper location.  Lets say that Machine1 is also DNS1 and
>
> WEB1
>
> > > then Machine1 has IP xxx.xxx.xxx and a request comes in for site
> >
> > number
> >
> > > 3 on the server then the DNS will point the request to site number
3
> >
> > and
> >
> > > with each request for a different site the DNS will point the
>
> request
>
> > in
> >
> > > the correct place?
> > >
> > > Mike
> > >
> > > -----Original Message-----
> > > From: Justin Williams [mailto:justin@naturalwebs.com]
> > > Sent: Wednesday, December 04, 2002 3:49 AM
> > > To: users@httpd.apache.org
> > > Subject: Re: [users@httpd] Beginner How-To
> > >
> > > OK.
> > > Presumably, then, this is a server which will have its own IP.  Is
> >
> > this
> >
> > > server
> > > to be co-located, or hosted in-house?
> > > If co-located, then the facility should have a DNS server to point
> > > domain
> > > names to your machine.  If they don't, or if you are hosting
>
> in-house,
>
> > > then
> > > you will need a DNS of your own.  This can be a separate machine,
or
> >
> > it
> >
> > > can
> > > be the same one.  Not a big issue, there.  The ISP I work for has
2
> >
> > DNSs
> >
> > > of
> > > its own to handle the websites we host.  Either way, if you are
>
> going
>
> > to
> >
> > > have
> > > multiple websites on there, then you need to have access to update
>
> the
>
> > > DNS
> > > server on a regular basis.  Every time you add a domain, you need
to
> >
> > be
> >
> > > able
> > > to update...
> > > If you are going to be serving up multiple sites to the world,
then
> >
> > yes,
> >
> > > you
> > > are going to need a static IP address.  It is possible to use
>
> dynamic,
>
> > > but
> > > that would *really* suck updating all of them every time your IP
> > > changes...
> > >
> > > On Wednesday 04 December 2002 01:20 pm, Michael Klama wrote:
> > > > This will be a production server hosting multiple sites out to
the
> > >
> > > rest
> > >
> > > > of the world.
> > > > Mike
> > > >
> > > > Visit our web site for great deals on Computers and Hardware and
>
> for
>
> > > > insightful and unique reviews of the latest hardware offerings
by
> >
> > all
> >
> > > of
> > >
> > > > the major manufacturers. www.l-and-m-associates.com
> > > >
> > > > -----Original Message-----
> > > > From: Justin Williams [mailto:justin@naturalwebs.com]
> > > > Sent: Wednesday, December 04, 2002 3:11 AM
> > > > To: users@httpd.apache.org
> > > > Subject: Re: [users@httpd] Beginner How-To
> > > >
> > > > Hi Michael
> > > > I recently set up my first server for an ISP that has always
been
>
> a
>
> > > > Windows
> > > > shop.  As the resident penguin-herder, there, I got my shoulder
> >
> > tapped
> >
> > > > when
> > > > they decided they wanted to give it a try.
> > > >
> > > > Most of your questions will be better answered if you can answer
> >
> > this
> >
> > > > one,
> > > > though: What are you setting up the server for?  I.e. are you
> >
> > setting
> >
> > > up
> > >
> > > > a
> > > > production server to send out pages to the rest of the world, or
>
> are
>
> > > you
> > >
> > > > setting up a testing server, that you only want visible to you
on
> >
> > your
> >
> > > > local
> > > > network?
> > > >
> > > > On Wednesday 04 December 2002 01:00 pm, Michael Klama wrote:
> > > > > Hello
> > > > > Can anyone point me in the right direction to find a beginners
> > >
> > > How-To
> > >
> > > > on
> > > >
> > > > > setting up the Apache web server?  I need the basic info on
how
>
> to
>
> > > set
> > >
> > > > > up the network coming into the web server, ie., Do I need a
>
> static
>
> > > IP,
> > >
> > > > > Do I need to set up my own DNS Server, Do I need to purchase a
> >
> > FQDN
> >
> > > > and
> > > >
> > > > > if so who can I purchase it from without using their hosting
> > >
> > > service?
> > >
> > > > > Currently I have high speed cable going to a linksys router
>
> which
>
> > > > > assigns IP addresses to all of my systems.  Will I still be
able
> >
> > to
> >
> > > > use
> > > >
> > > > > this setup?
> > > > > As you can see I have a lot of basic questions I need answered
> > >
> > > before
> > >
> > > > I
> > > >
> > > > > can start serving web pages to the internet.  Any advise would
>
> be
>
> > > > > greatly appreciated
> > > > >
> > > > > Mike
>
> ---------------------------------------------------------------------
>
> > > > > 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
> >
> >
---------------------------------------------------------------------
> >
> > > > 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
>
> ---------------------------------------------------------------------
>
> > > 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
> >
> >
> >
> >
> >
---------------------------------------------------------------------
> > 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
>
>
>
>
> ---------------------------------------------------------------------
> 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




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