Bob Kline wrote:
On 2/25/2007 11:14 AM, [some other] Bob wrote:
Take a look at PR 39710
(http://issues.apache.org/bugzilla/show_bug.cgi?id=39710), this seems
to be quite similar to me.
Yes, thanks, this does look the same problem.
I've been trying to channel the follow-on
On 5/27/07, Bob Kline [EMAIL PROTECTED] wrote:
Bob Kline wrote:
On 2/25/2007 11:14 AM, [some other] Bob wrote:
Take a look at PR 39710
(http://issues.apache.org/bugzilla/show_bug.cgi?id=39710), this seems
to be quite similar to me.
Yes, thanks, this does look the same problem.
I've
Joshua Slive wrote:
In the case of this particular bug, if you look at the developer's
list, you'll see lots of action happening, including a fix on trunk
and a proposal to backport to 2.2.
Excellent news, thanks! And thanks for the tip on where to *really*
find information on the Apache bug
On 2/25/2007 11:14 AM, Bob wrote:
Take a look at PR 39710
(http://issues.apache.org/bugzilla/show_bug.cgi?id=39710), this seems
to be quite similar to me.
Yes, thanks, this does look the same problem. It would appear from the
comments in the PR that mod_cgid didn't get hit with this bug.
On Sun, 25 Feb 2007 01:11:05 -0500
Bob Kline [EMAIL PROTECTED] wrote:
HTTP/1.1 500 Internal Server Error
Date: Sun, 25 Feb 2007 03:16:46 GMT
Server: Apache/2.2.3 (Debian)
Content-Length: 0
Connection: close
Content-Type: text/x-python
Insufficient information. What's the actual error
Nick Kew wrote:
Insufficient information. What's the actual error here?
Can't run the script (if so why?) Runs but crashes?
Runs OK but generates an HTTP error within the script?
Or???
The script throws an exception before sending any output to the standard
output file. Here's what's in
Bob Kline wrote:
Before filing a bug report, I want to check with the list to see if I'm
missing something or if this is a known bug and I just haven't found it
in the database.
Take a look at PR 39710
(http://issues.apache.org/bugzilla/show_bug.cgi?id=39710), this seems to
be quite similar
Before filing a bug report, I want to check with the list to see if I'm
missing something or if this is a known bug and I just haven't found it
in the database.
I'm upgrading my server and Apache will be jumping from 2.0.46 to 2.2.3.
I noticed when testing things on the new box that Apache's
