Re: [SQU] Access.log Data Filtering

On Thu, 7 Dec 2000, Andrea Lain wrote:

>
> Hello all,
>
> Thanks for the help received in analyzing certain entries in the access.log
> file. Now I have one more question along these same lines:
>
> When filtering the access.log file with a script, we would like to be able
> to differentiate between unique user requests and those generated by the
> system. For example, when we hit a site such as Microsoft.com, the
> access.log file shows a GET for the initial page, then subsequent CONNECT
> requests (sometimes also GET requests) for items such as images.
>
> We have built a custom script that filters this information to display only
> requests for text/html and application data by URL. However, we are still
> being presented with quite a bit of data and some of it is redundant. So we
> are wondering if there's a more efficient way to filter the access.log to
> return only requests initiated by the user and not include any subsequent
> requests (like graphic accesses) that the system will initiate. Is there a
> different field we can filter by that will narrow down this criteria?

I don't think its possible. There isn't really anything in HTTP that
tells you why user/browser makes a request.

You might have luck by looking at the Referer field. If you enable referer
logging or log full headers with squid, you can get those headers.

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html