[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#164688: marked as done (Developing CGI scripts & apache2 -> hell)

Your message dated Thu, 02 Jun 2016 23:24:23 +0200
with message-id <3541105.lT7o13sHNN@k>
and subject line Developing CGI scripts & apache2 -> hell
has caused the Debian Bug report #164688,
regarding Developing CGI scripts & apache2 -> hell
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
164688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=164688
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apache2
Version: 2.0.42-2
Severity: wishlist
Tags: upstream

As we agreed ...

----- Forwarded message from Thom May <thom@debian.org> -----

Date: Mon, 14 Oct 2002 13:27:24 +0100
From: Thom May <thom@debian.org>
To: Sander Smeenk <ssmeenk@debian.org>
Subject: Re: Developing CGI scripts & apache2 -> hell

* Sander Smeenk (ssmeenk@debian.org) wrote :
> Hi,
> 
> Apache2 gets nicer and nicer, but I still hate this behaviour:
> 
> I have a CGI script I develop, and I need to output a Dump of a hash.
> As with all CGI scripts I develop I use:
> 
> print STDERR Dumper(\@arrayofhashes)
> 
> Apache 1.3.22 just outputs to the errorlog:
> 
> | $VAR1 = [
> |           {
> |             'text' => '123',
> |             'in_reply' => 1,
> |             'forum_id' => 5
> |           }
> |         ];
> 
> But with Apache2 it looks like this:
> 
> | [Mon Oct 14 14:19:51 2002] [error] [client 192.168.1.2] $VAR1 = [, referer: http://misery.freshdot.net/~ssmeenk/topicList.pl?forum=1
> | [Mon Oct 14 14:19:51 2002] [error] [client 192.168.1.2]           {, referer: http://misery.freshdot.net/~ssmeenk/topicList.pl?forum=1
> | [Mon Oct 14 14:19:51 2002] [error] [client 192.168.1.2]             'text' => '123',, referer: http://misery.freshdot.net/~ssmeenk/topicList.pl?forum=1
> | [Mon Oct 14 14:19:51 2002] [error] [client 192.168.1.2]             'in_reply' => '1',, referer: http://misery.freshdot.net/~ssmeenk/topicList.pl?forum=1
> | [Mon Oct 14 14:19:51 2002] [error] [client 192.168.1.2]             'forum_id' => '1',, referer: http://misery.freshdot.net/~ssmeenk/topicList.pl?forum=1
> | [Mon Oct 14 14:19:52 2002] [error] [client 192.168.1.2]           }, referer: http://misery.freshdot.net/~ssmeenk/topicList.pl?forum=1
> | [Mon Oct 14 14:19:52 2002] [error] [client 192.168.1.2]         ];, referer: http://misery.freshdot.net/~ssmeenk/topicList.pl?forum=1
> 
> Now this looks OK when not wrapped, but it's very annoying when you get
> all these messages in a tail in your xterm, wrapped and all.  Is there a
> way to tell Apache that not all messages printed by scripts are errors,
> and that it doesn't need to print the full [date] [type] [client]
> [error] [referer] line ?
> 
Not so far as I know.

> If not, can it be changed easily in the source, so that it reflects the
> way Apache 1.3 works?  I can't think of a situation where you'd want to
> have all this information for a script error, or a missing image for
> instance. ;)

Yeah, definitely. I think this is a good idea.
> 
> If you want me to, i'll file this as a wishlist bug.
> 
Please, and tag it upstream (i'm feeling very tired and lazy today :)  )
-Thom

----- End forwarded message -----

Thanks,
Sander.

-- 
| One tequila, two tequila, three tequila, floor.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

--- End Message ---
--- Begin Message --- 
> Now this looks OK when not wrapped, but it's very annoying when you get
> all these messages in a tail in your xterm, wrapped and all.  Is there a
> way to tell Apache that not all messages printed by scripts are errors,
> and that it doesn't need to print the full [date] [type] [client]
> [error] [referer] line ?
> 

Apache 2.4 has ErrorLogFormat which allows some control over the format. It's likely that this can be used to get a more readable output for the cgi error messages.

Apart from that, the trend in Apache httpd is to always include where a specific log message came from and not allow things to simply write to the log file without format strings.  Therefore it is unlikely that your suggestion is implemented further than what ErrorLogFormat allows and I am closing this bug.

--- End Message ---
Reply to: