Bug #1863

cgi logging doesn't work in v. 1.4.20

Added by johnny9 over 5 years ago. Updated over 5 years ago.

Status:FixedStart date:2008-12-30
Priority:LowDue date:
Assignee:-% Done:

100%

Category:-
Target version:1.4.24
Missing in 1.5.x:

Description

The cgi output isn't logged anywhere, so it's basically impossible to debug/log in any cgi application. I think this will seriously hinder the acceptance of lighty .20.


Related issues

Related to Bug #1836: no stderr from cgi scripts Duplicate 2008-12-04

Associated revisions

Revision 2550
Added by stbuehler over 5 years ago

Add server.breakagelog, a "special" stderr (fixes #1863)

  • The breakage-log simply replaces stderr (the old stderr is moved away if needed for errorlog),
    and stderr isn't closed after forking.
    It defaults to stderr if started with -n (no daemonize), otherwise it defaults to /dev/null.
    It is not reopened in log_error_cycle, as there may be many long running childs which have it
    still open anyway. Use a pipe-logger with cycle-support if you need it.

Revision 2552
Added by stbuehler over 5 years ago

Add server.breakagelog, a "special" stderr (fixes #1863)

  • The breakage-log simply replaces stderr (the old stderr is moved away if needed for errorlog),
    and stderr isn't closed after forking.
    It defaults to stderr if started with -n (no daemonize), otherwise it defaults to /dev/null.
    It is not reopened in log_error_cycle, as there may be many long running childs which have it
    still open anyway. Use a pipe-logger with cycle-support if you need it.

History

#1 Updated by plan9grid over 5 years ago

The CGI error logging facility that was present previously was very useful to me. Hopefully this functionality can be re-integrated.

#2 Updated by nitrox over 5 years ago

  • Priority changed from High to Low
  • Target version changed from 1.4.20 to 1.4.21

#3 Updated by icy over 5 years ago

  • Target version changed from 1.4.21 to 1.4.22

#4 Updated by stbuehler over 5 years ago

  • Target version changed from 1.4.22 to 1.4.23

#5 Updated by stbuehler over 5 years ago

  • Target version changed from 1.4.23 to 1.4.24

#6 Updated by stbuehler over 5 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset r2550.

Also available in: Atom