Changes between Version 13 and Version 14 of web_server_logs


Ignore:
Timestamp:
Aug 17, 2017, 11:23:25 AM (4 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • web_server_logs

    v13 v14  
    1212
    1313If your web site is being used to organize, your web logs are at risk of being subpoenaed. May First/People Link has a long [wiki:/legal history] of fighting such requests, however, you may want to read on to find out how you can better protect your people.
    14 
    15 == May First/People Link web server logging ==
    16 
    17 At May First/People Link you have the option to enable or disable logging.
    18 
    19 If it is enabled, you can see the logs for any web site from your organization by looking in the filesystem on your primary server.  For example, if the member organization named `foo` has a web site named `example.org`, the logs for that web site can be found at:
    20 {{{
    21 /home/members/foo/sites/example.org/logs/
    22 }}}
    23 
    24 In that directory, the file named `web.log` is the most recent log, `web.log.1` is from the previous full week, and `web.log.2.gz`, `web.log.3.gz`, etc. are compressed logs from previous weeks.  (This is the [http://httpd.apache.org/docs/current/logs.html#accesslog Apache access log].)
    25 
    26 In addition, you will see `error.log`, which has the same naming convention. The `web.log` files are "access" logs - meaning they have a line for every item on your web site that was requested. `error.log` shows errors that were encountered.
    27 
    28 These logs, written to by the Apache web server that runs your site, and will include any PHP errors and notices caused by your site.  This is useful for diagnosing errors in the functioning of your site and checking for potential problems indicated by notices.  In short, read Apache logs for [http://docs.php.net/manual/en/function.error-log.php PHP errors]. 
    2914
    3015== Turn On web logging ==
     
    5439Please note - just removing the Log lines will not disable logging, it will simply cause your logging to happen in the server-wide logs. You must configure your site to explicitly log to /dev/null.
    5540
     41=== Is that all? ===
    5642
     43Turning off web logging is a good first step, but it is not all.
     44
     45If you are using a service like Google analytics - then all the data is going straight to Google. There is nothing you can do about that except disable Google Analytics on your site.
     46
     47Additionally, if you are using Google Fonts, incorporating Facebook or Twitter code into your site, or pulling data from other services like this - then every visitor to your site is being logged by Google, Facebook, Twitter, etc. Some steps you can take to mitigate this problem include:
     48
     49 * Download all fonts to your site - so each visitor doesn't have to make a request to Google or wherever the font is stored
     50 * Download all social media icons to your site rather than have each visitor load them from Google, Facebook, etc. In addition, don't use javascript provided by these companies - instead, create your own links so people who choose to repost via Twitter or Facebook can click on a link that will open a new page in Twitter or Facebook - but people who choose not to click on those links do not have their privacy compromised.
     51
     52== Accessing your logs ==
     53
     54At May First/People Link you have the option to enable or disable logging.
     55
     56If it is enabled, you can see the logs for any web site from your organization by looking in the filesystem on your primary server.  For example, if the member organization named `foo` has a web site named `example.org`, the logs for that web site can be found at:
     57{{{
     58/home/members/foo/sites/example.org/logs/
     59}}}
     60
     61In that directory, the file named `web.log` is the most recent log, `web.log.1` is from the previous full week, and `web.log.2.gz`, `web.log.3.gz`, etc. are compressed logs from previous weeks.  (This is the [http://httpd.apache.org/docs/current/logs.html#accesslog Apache access log].)
     62
     63In addition, you will see `error.log`, which has the same naming convention. The `web.log` files are "access" logs - meaning they have a line for every item on your web site that was requested. `error.log` shows errors that were encountered.
     64
     65These logs, written to by the Apache web server that runs your site, and will include any PHP errors and notices caused by your site.  This is useful for diagnosing errors in the functioning of your site and checking for potential problems indicated by notices.  In short, read Apache logs for [http://docs.php.net/manual/en/function.error-log.php PHP errors]. 
     66
     67