Project

General

Profile

Actions
Copy link

Bug #121

closed

Content Length Not Written to Log File

Added by Anonymous almost 20 years ago. Updated over 16 years ago.

Status:
Invalid
Priority:
Normal
Category:
mod_accesslog
Target version:
-
ASK QUESTIONS IN Forums:

Description

With source:/trunk#350 of lighttpd the content length log file field ({{{%b}}}) is always written as {{{-}}-}. In the 1.3._x_ series of releases it was correctly written as the length of the content returned to the browser. This makes it impossible to determine the amount of data a site has transferred from it's log files.

For example:


216.148.212.188 - - [10/May/2005:02:10:30 +1200] "GET /feed.atom HTTP/1.1" 200 - "-" "Bloglines/2.0 (http://www.bloglines.com)"

-- lighttpd.net

Actions
Copy link
 #1

Updated by conny about 19 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

Content length ("bytes outgoing" in documentation) is represented by "%O".

Actions
Copy link
 #2

Updated by stbuehler over 16 years ago

  • Status changed from Fixed to Invalid
Actions
Copy link

Also available in: Atom