[NTLUG:Discuss] Re: Real dangers of CR2

[David Camm]

while ssl support is now built into the latest versions of apache, in
order for it to work, 
you need a certificate from a CA (certification authority) like Verisign
or Thawte, which is not free. Thawte is currently charging $125/year (i
think).

also, if you change your url to https://www.mydomain.com/ think of the
<exaggerate>hundreds of thousands </exaggerate> of surfers who have hit
your site and can't find it any more.

this is NOT a real-world solution for personal websites.

david camm
advanced web systems

Daniel Hauck wrote:
> 
> Obviously some of us survived and some of us didn't.  That's not to say they
> aren't getting around to it later though...
> 
> My brother's machine is still web-available as is mine and we are in vastly
> different areas.  I think they merely shut down some of the ones producing
> higher traffic.  It has definitely made a difference though... I am down to
> only 100+ hits per day now as opposed to the previously higher rate of 500+.
> (rates are guestimated, not measured and then approximated.)  I hope they
> don't block us all off or I will be forced to seek other alternatives in my
> web hosting efforts...like running on port 8080 or 81 or something like
> that... I hate non-standard ports though... it's just kinda ugly...oh
> wait... :)  I GOT IT!!!
> 
> To anyone wondering what do to?  How about setting up HTTPS!!  That's not
> port 80 either!!  Most people would not object to allowing a secure
> connection either!  The other part of the work-around would be setting up
> alternative server names like "secure.domain.com" or the like as the
> redirected point of service.  I think that's a happy alternative for those
> with a blockage of port 80.
> 
> ----- Original Message -----
> From: "Fred James" <fredjame at concentric.net>
> To: <discuss at ntlug.org>
> Sent: Friday, August 10, 2001 3:59 PM
> Subject: Re: [NTLUG:Discuss] Re: Real dangers of CR2
> 
> > My attempt to access your site produced:
> > >>
> > This browser does not implement CSS properly. To view this site you need
> > to download ia more recent browser. Microsoft Internet Explorer 4.0+ or
> > Netscape 6.0+ will work fine. To view a listing of CSS-compatible
> > browsers, go to http://www.w3.org/Style/CSS/#browsers.
> >
> >  In the meantime, you can read my LiveJournal here.
> > <<
> > I am running Netscape Communicator 4.76 - just though you would like to
> > know.
> >
> >
> > Travis Bell wrote:
> > >
> > > On Fri, Aug 10, 2001 at 12:49:21PM -0500, Steve Egbert wrote:
> > > > I am not particularily pleased when AT&T @Home shutted port 80 off.  A
> brief
> > > > chat with AT&T Customer Representative Staff states that this measure
> is a
> > > > permanent and indefinite measure.
> > >
> > > Am I the only AT&T @Home user who did _NOT_ get shut down?  I can still
> > > access my site (running on my home PC) from anywhere.  All of my friends
> > > can still get to it, and I can still see it from work, too.
> > >
> > > http://tjbell.dhs.org
> > >
> > > All of this days after the AT&T announcement.  I don't get it...
> > >
> > > --
> > > Travis Bell  a.k.a.  MudPoet
> > > echo tjbexx at usa.nyz | tr xyz let
> > > ICQ: 6014042  -  AIM: MudPoet
> > > http://tjbell.dhs.org
> > > _______________________________________________
> > > http://www.ntlug.org/mailman/listinfo/discuss
> >
> > --
> > ...make every program a filter...
> > _______________________________________________
> > http://www.ntlug.org/mailman/listinfo/discuss
> >
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss