<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: webalizer or analog equivalent for SSL-based access_logs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638930#M851808</link>
    <description>access_logs for https (SSL) vs. http (non-SSL) are the same.  We use analog for both.</description>
    <pubDate>Fri, 04 Jan 2002 17:43:28 GMT</pubDate>
    <dc:creator>Christopher Caldwell</dc:creator>
    <dc:date>2002-01-04T17:43:28Z</dc:date>
    <item>
      <title>webalizer or analog equivalent for SSL-based access_logs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638929#M851807</link>
      <description>Hi all, &lt;BR /&gt;&lt;BR /&gt;Anyone knows of a freeware that allows statistical parsing of ssl_request_logs (HTTP-SSL access_logs) the same way webalizer and analog does for access_log (HTTP access_logs) for Apache+SSL webserver? &lt;BR /&gt;&lt;BR /&gt;Thanks in advance. Regards. &lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong &lt;BR /&gt;Brainbench MVP for Unix Admin &lt;BR /&gt;&lt;A href="http://www.brainbench.com" target="_blank"&gt;http://www.brainbench.com&lt;/A&gt;</description>
      <pubDate>Fri, 04 Jan 2002 09:54:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638929#M851807</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-01-04T09:54:08Z</dc:date>
    </item>
    <item>
      <title>Re: webalizer or analog equivalent for SSL-based access_logs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638930#M851808</link>
      <description>access_logs for https (SSL) vs. http (non-SSL) are the same.  We use analog for both.</description>
      <pubDate>Fri, 04 Jan 2002 17:43:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638930#M851808</guid>
      <dc:creator>Christopher Caldwell</dc:creator>
      <dc:date>2002-01-04T17:43:28Z</dc:date>
    </item>
    <item>
      <title>Re: webalizer or analog equivalent for SSL-based access_logs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638931#M851809</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Two lines of access_log:&lt;BR /&gt;&lt;BR /&gt;202.156.255.212 - - [04/Dec/2001:18:47:22 +0800] "GET /scripts/..%252f../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 294 "-" "-"&lt;BR /&gt;127.0.0.1 - - [05/Dec/2001:09:34:56 +0800] "get" 501 - "-" "-"&lt;BR /&gt;&lt;BR /&gt;Two lines of ssl_request_log:&lt;BR /&gt;&lt;BR /&gt;[05/Jan/2002:07:28:27 +0800] 192.168.123.120 SSLv3 RC4-MD5 "POST /cgi-bin/itrc.cgi HTTP/1.1" 7293&lt;BR /&gt;[05/Jan/2002:07:28:56 +0800] 192.168.123.120 SSLv3 RC4-MD5 "GET /cgi-bin/itrc.cgi HTTP/1.1" 534&lt;BR /&gt;&lt;BR /&gt;Their formatting is different. Anyway, I found out later that access_log uses the LogFormat setting in httpd.conf while ssl_request_log uses the CustomLog setting in httpd.conf.&lt;BR /&gt;&lt;BR /&gt;Thanks. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong&lt;BR /&gt;Brainbench MVP for Unix Admin&lt;BR /&gt;&lt;A href="http://www.brianbench.com" target="_blank"&gt;http://www.brianbench.com&lt;/A&gt;</description>
      <pubDate>Fri, 04 Jan 2002 23:54:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638931#M851809</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-01-04T23:54:10Z</dc:date>
    </item>
    <item>
      <title>Re: webalizer or analog equivalent for SSL-based access_logs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638932#M851810</link>
      <description>Either&lt;BR /&gt;1) tell analog what format the logs are in (see &lt;A href="http://analog.cx/docs/logfmt.html)" target="_blank"&gt;http://analog.cx/docs/logfmt.html)&lt;/A&gt;&lt;BR /&gt;or&lt;BR /&gt;2) tell apache/iPlanet/Netscape etc. what format you'd like the log files to be in (see the documentation for your web server).&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 07 Jan 2002 13:54:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638932#M851810</guid>
      <dc:creator>Christopher Caldwell</dc:creator>
      <dc:date>2002-01-07T13:54:10Z</dc:date>
    </item>
    <item>
      <title>Re: webalizer or analog equivalent for SSL-based access_logs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638933#M851811</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;In my first response, I had already updated CustomLog to tailor ssl_request_log to use the same format as LogFormat which is used to tailor access_log which fixed my issue.&lt;BR /&gt;&lt;BR /&gt;Anyway, thanks for the information. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong&lt;BR /&gt;Brainbench MVP for Unix Admin&lt;BR /&gt;&lt;A href="http://www.brainbench.com" target="_blank"&gt;http://www.brainbench.com&lt;/A&gt;</description>
      <pubDate>Mon, 07 Jan 2002 14:26:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/webalizer-or-analog-equivalent-for-ssl-based-access-logs/m-p/2638933#M851811</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-01-07T14:26:48Z</dc:date>
    </item>
  </channel>
</rss>

