[BlueOnyx:23594] Re: AWStats likely incomplete

[Adam Lepp]

This shouldn't make a difference. I just want to it to run statistics for all pages.

-----Original Message-----
From: Blueonyx <blueonyx-bounces at mail.blueonyx.it> On Behalf Of Brent Epp
Sent: Monday, January 20, 2020 12:39 PM
To: BlueOnyx General Mailing List <blueonyx at mail.blueonyx.it>
Subject: [BlueOnyx:23593] Re: AWStats likely incomplete

I'm not familiar enough with AWStats particularly to know why this change may have affected it, but I can tell you that Javascript can be finicky with redirection and it will cause navigation step.  Perhaps that step is what's affecting the stats?  We would need to know specifically what metric or metrics have changed.

The first thing I would do is remove the JS redirect and use an .htaccess file for SSL enforcement.  You'll need to login to the BX admin GUI, under Server Management > Network Services > Web

Under Options: enable All, FollowSymLInks, SymLinksIfOwnerMatch Under AllowOverride: enable All, Options

If these are already enabled, you can just leave this screen alone.

Then paste this inside a file named `.htaccess` in the website's document root:

----------------------------

DirectoryIndex index.cgi

# enable rewrites
Options +FollowSymLinks
RewriteEngine on
RewriteBase /

# force SSL
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

----------------------------

This will do two things:
  - set your default homepage to index.cgi (no redirection needed)
  - force SSL throughout the entire site transparently

If for some reason the .htaccess file breaks the site, you can quickly restore access by renaming the .htaccess file to anything else (like
.htaccess.off)

  - Brent

On 2020-01-20 10:53, Adam Lepp wrote:
> 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-bounces at mail.blueonyx.it> On Behalf Of Brent 
> Epp
> Sent: Monday, January 20, 2020 11:10 AM
> To: BlueOnyx General Mailing List <blueonyx at 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 it’s due to my recently-added 
>> directive that the site now requires SSL.
>>
>> I looked over documentation but don’t 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 at mail.blueonyx.it
>> http://mail.blueonyx.it/mailman/listinfo/blueonyx
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx
>
>
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx
>

_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx