Index.html redirects via JS to https://[sitename]/index.cgi but you can access http://[sitename]/index.cgi directly. They have a larger site that most people use, via a menu item, to access this site. We had recently changed the directive from http://[sitename]/index.cgi to https://[sitename]/index.cgi and that's what I believe caused this.
-----Original Message----- From: Blueonyx <blueonyx-boun...@mail.blueonyx.it> On Behalf Of Brent Epp Sent: Monday, January 20, 2020 11:10 AM To: BlueOnyx General Mailing List <blueonyx@mail.blueonyx.it> Subject: [BlueOnyx:23591] Re: AWStats likely incomplete Hi Adam, How exactly did you implement the SSL enforcement? - Brent On 2020-01-20 09:55, Adam Lepp wrote: > > One of my clients pulls her AWStats monthly. We noticed that recent > stats have dropped off 50%+ and suspect its due to my recently-added > directive that the site now requires SSL. > > I looked over documentation but dont see an easy way to make sure it > is reading all page requests. > > With Webalizer, hits dropped somewhat due to the usual holiday > slowdown, but not to the extreme shown by AWStats. We prefer to > continue using AWStats. > > Can any of you smart people provide insight, and a way to adjust > configuration logs without messing anything up? > > I could edit the raw logs, replace HTTPS with HTTP and run on a > different server, but there has to be an easier way. > > 5209R BOPE > > > _______________________________________________ > Blueonyx mailing list > Blueonyx@mail.blueonyx.it > http://mail.blueonyx.it/mailman/listinfo/blueonyx _______________________________________________ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx _______________________________________________ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx