Re: converting my local site to be https only access
On Sunday 30 April 2017 20:19:21 firstname.lastname@example.org wrote:
> On Sun, 30 Apr 2017, Gene Heskett wrote:
> > On Saturday 29 April 2017 14:49:04 Gene Heskett wrote:
> >> On Saturday 29 April 2017 14:21:27 Jochen Spieker wrote:
> >>> Gene Heskett:
> >>>> On Saturday 29 April 2017 04:05:01 Felix Dietrich wrote:
> >>>>> Gene Heskett <email@example.com> writes:
> >>>>>> Where can I find a tut that is a complete instruction set to
> >>>>>> have it do an auto-redirect to itself, but using the "s" stuff
> >>>>>> regardless of the accessing client as long as the client can
> >>>>>> handle the https stuff this conversion will return to the
> >>>>>> client?
> >>> What you want to do requires that you understand the basics of
> >>> Apache's configuration mechanism. You should really start with
> >>> that.
> >>> http://httpd.apache.org/docs/2.4/en/getting-started.html
> >>> http://httpd.apache.org/docs/2.4/en/bind.html
> >>> http://httpd.apache.org/docs/2.4/en/configuring.html
> >>> http://httpd.apache.org/docs/2.4/en/urlmapping.html
> >>> http://httpd.apache.org/docs/2.4/en/vhosts/
> > I don't have 2.4, 2.2 here on wheezy.
> > Looking in the docs/2.2/envvars reference and trying some of the
> > commands I find I apparently must specify the port # somehow.
> > apache2ctl cannot connect on port 80. It apparently uses
> > /etc/alternatives/www-browser, which is a softlink to
> > /usrt/bin/lynx, and guess what?
> > lynx support at lynx.isc.org has been deleted. And it won't work
> > without talking to isc.org first. Even after being re-installed.
> Lynx works just fine. I expect your configuration file simply has some
> references to obsolete remote locations.
> Does this work?
> $ WWW_HOME="https://en.wikipedia.org/wiki/PEBKAC" lynx
> or this?
> And does this...
> $ grep '^STARTFILE:' /etc/lynx-cur/lynx.cfg
> ...confirm that you have something obsolete like
> in your lynx.cfg ?
> Then fix that broken reference. Edit /etc/lynx-cur/lynx.cfg, replacing
> that STARTFILE url with whatever you like.
> FWIW, I think
> makes a sensible default.
except I am then trapped in my home dir.
> Or, if for some incomprehensible reason you think a remote website is
> an appropriate default startfile, you could use
> While you're at it, you might want to cast your eye over any other
> lines returned by this...
> $ grep '^[A-Z_]*:[[:blank:]]*https\?://' /etc/lynx-cur/lynx.cfg
Which was a wisc.edu url.
> ...and see if you wouldn't rather change them to something more
> up-to-date, more reliable, or more appropriate for your installation.
> > So A: file a bug against lynx, best to remove it as its apparently
> > been EOL'd by isc.org
> Huh? You would remove a program simply because isc.org removes a
> couple web pages?
> Development of lynx continues unabated:
Sorta seems to me that ought to be kept uptodate in re that by the debian
> Good luck with your project.
I have atm, the darnest collection of Murphy's work I've ever seen. So I
am inclined to fire up amrecover, back it up a week, and recover
the /etc/apache2, /etc/httpd, and /var/www/html trees. That sould put
me back to a working, non ssl, web server. All this got started because
the next firefox says it will not look at a plain http site, and I was
trying to make robots.txt kick googlebot in the gonads and out of my
site, its eating more #$%& bandwidth than my site traffic is. So once
I've restored normal http operations, I'll come back and see if I can
find some help converting it to https.
Thank you firstname.lastname@example.org.
Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>