More information out of error log?

[Ilan Berkner]

So I turned on the access log but I'm concerned that its size is getting
larger by the second (and this is off peak).  By tomorrow AM, its size may
exceed available disk space.

Is there a way to programmatically turn it on or off via the configuration
file depending on whether or not an error was generated or a particular type
of URL requested?

On Tue, Jan 13, 2009 at 6:05 PM, Ilan Berkner <iberkner at gmail.com> wrote:

> Hi All,
>
> We are getting many of these errors:
>
> 2009/01/13 13:04:28 [error] 27100#0: *782718 open()
> "/home/spellcit/public_html/letters/.mp3" failed (2: No such file or
> directory), client: 204.38.160.220, server: www.spellingcity.com, request:
> "GET /letters/.mp3 HTTP/1.1", host: "www.spellingcity.com"
> Essentially one of 2 things is happening:
>
> (1) One of our php or flash files is trying to access this invalid file
> "/letters/.mp3" or
> (2) A user is trying to access this directly (unlikely).
>
> The problem is that the log entry does not on the surface reveal enough
> information about where the request is coming from so we're having a tough
> time identifying the source of the request.  Is there a way (is it possible)
> to add more information to the log entry to better identify the source of
> the request (swf, php, html, direct, etc.).
>
> Thanks
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20090113/34a13085/attachment.html>