Project

General

Profile

Actions

Bug #493

closed

file logging issue when stream.depth is reached

Added by Victor Julien over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Reported privately: "I found that when an HTTP session has a client download a file larger than the ‘stream.depth’ configuration setting, the ‘log-file’ module which writes in JSON format doesn’t log the file at all, and the ‘log-filestore’ module does not call the ‘LogFilestoreLogCloseMetaFile()’ function so some of the meta data is missing, both of which I believe are because the state is still set to FILE_STATE_OPENED. I’m not sure if this as-designed or something that should be fixed, at least the JSON logging, since filestore works to an extent even in this scenario."

Actions

Also available in: Atom PDF