Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #180567
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: converting my local site to be https only access |
| Date | 2017-05-01 03:40 +0200 |
| Message-ID | <tC8tH-2oO-5@gated-at.bofh.it> (permalink) |
| References | <tBroJ-AM-1@gated-at.bofh.it> <tC4gq-8jL-11@gated-at.bofh.it> <tC7eh-1FK-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sunday 30 April 2017 20:19:21 davidson@freevolt.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 <gheskett@shentel.net> 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? > > $ > WWW_HOME="file://localhost/REPLACE-ME-WITH-A-PATH-TO-SOME-LOCAL-HTML-D >OC.html" lynx > > And does this... > > $ grep '^STARTFILE:' /etc/lynx-cur/lynx.cfg > > ...confirm that you have something obsolete like > > STARTFILE:http://lynx.isc.org/ > > in your lynx.cfg ? > it was. > Then fix that broken reference. Edit /etc/lynx-cur/lynx.cfg, replacing > that STARTFILE url with whatever you like. > > FWIW, I think > > STARTFILE:file://localhost/~/ > > 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 > > STARTFILE:http://lynx.invisible-island.net/ > > instead. > > 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: > > http://invisible-island.net/lynx/lynx-develop.html Sorta seems to me that ought to be kept uptodate in re that by the debian folks. > 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 davidson@freevolt.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>
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-04-29 05:40 +0200
Re: converting my local site to be https only access Felix Dietrich <felix.dietrich@sperrhaken.name> - 2017-04-29 10:30 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-04-29 15:10 +0200
Re: converting my local site to be https only access Jochen Spieker <ml@well-adjusted.de> - 2017-04-29 20:30 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-04-29 20:50 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-04-30 23:10 +0200
Re: converting my local site to be https only access Dejan Jocic <jodejka@gmail.com> - 2017-04-30 23:50 +0200
Re: converting my local site to be https only access Eike Lantzsch <zp6cge@gmx.net> - 2017-05-01 00:00 +0200
Re: converting my local site to be https only access davidson@freevolt.org - 2017-05-01 02:20 +0200
Re: converting my local site to be https only access Lisi Reisz <lisi.reisz@gmail.com> - 2017-05-01 03:00 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-05-01 03:40 +0200
Re: converting my local site to be https only access davidson@freevolt.org - 2017-05-01 21:50 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-05-01 03:40 +0200
Re: converting my local site to be https only access Greg Wooledge <wooledg@eeg.ccf.org> - 2017-05-01 15:30 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-05-01 16:10 +0200
Re: converting my local site to be https only access rhkramer@gmail.com - 2017-05-01 17:20 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-05-01 19:00 +0200
Re: converting my local site to be https only access rhkramer@gmail.com - 2017-05-01 21:00 +0200
Re: converting my local site to be https only access rhkramer@gmail.com - 2017-05-01 21:00 +0200
Re: converting my local site to be https only access davidson@freevolt.org - 2017-05-02 01:40 +0200
Re: converting my local site to be https only access Ric Moore <wayward4now@gmail.com> - 2017-05-03 18:40 +0200
Re: converting my local site to be https only access Jonathan Dowland <jmtd@debian.org> - 2017-05-02 12:40 +0200
Re: converting my local site to be https only access <tomas@tuxteam.de> - 2017-05-02 13:30 +0200
Re: converting my local site to be https only access Jonathan Dowland <jmtd@debian.org> - 2017-05-02 23:20 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-05-02 23:40 +0200
Re: converting my local site to be https only access <tomas@tuxteam.de> - 2017-05-03 11:30 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-05-03 14:40 +0200
Re: converting my local site to be https only access <tomas@tuxteam.de> - 2017-05-03 15:30 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-05-02 22:50 +0200
Re: converting my local site to be https only access Jonathan Dowland <jmtd@debian.org> - 2017-05-02 23:20 +0200
Re: converting my local site to be https only access Gene Heskett <gheskett@shentel.net> - 2017-05-02 23:50 +0200
csiph-web