httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steffen" <i...@apachelounge.com>
Subject Re: [VOTE] Apache 2.2.6, 2.0.61 and 1.3.39 release candidate tarballs for review
Date Thu, 06 Sep 2007 19:35:14 GMT
I did, not sure the guy from the report below did.

The author(s) of mod_fcgid looking at the issue right now. Do not expect 
that there is a solution from them soon.

I do not now how many users are affected by the bug(s) in 2.2.6 . I guess 
there are thousands users running mod-fcgid , special heavy loaded sites. 
The guess is based on the ~80.000 downloads of 2.2.4 from the 
www.apachelounge.com . And also now a days quite some users  Win 32 building 
Apache.

Steffen

----- Original Message ----- 
From: "Jim Jagielski" <jim@jaguNET.com>
To: <dev@httpd.apache.org>
Sent: Thursday, 06 September, 2007 17:53
Subject: Re: [VOTE] Apache 2.2.6, 2.0.61 and 1.3.39 release candidate 
tarballs for review


> Did you rebuild mod_fcgid?
>
> On Sep 6, 2007, at 11:08 AM, Steffen wrote:
>
>> An other report:
>>
>> mod_cgi is working OK for me with the Apache 2.2.6 RC, which I built
>> with VC6 - not VC8, on Win2k sp4.
>>
>> I can run the Apache-provided /cgi-bin/printenv.pl test Perl program
>> with no problems.
>>
>> mod_fcgid is not working for me, either with Perl or with my own FCGI
>> test program.
>>
>> Steffen
>>
>> ----- Original Message ----- From: "Jim Jagielski" <jim@jaguNET.com>
>> To: <dev@httpd.apache.org>
>> Cc: <testers@httpd.apache.org>
>> Sent: Thursday, 06 September, 2007 15:48
>> Subject: Re: [VOTE] Apache 2.2.6, 2.0.61 and 1.3.39 release  candidate 
>> tarballs for review
>>
>>
>>>
>>> On Sep 4, 2007, at 5:29 PM, Jim Jagielski wrote:
>>>
>>>> Available for your testing pleasure, 3, count 'em, 3
>>>> Apache HTTP Server release candidate tarballs, located,
>>>> as expected at:
>>>>
>>>>     http://httpd.apache.org/dev/dist/
>>>>
>>>> This vote will run through Sept 6, 2007 and close
>>>> Sept 7, unless otherwise noted...
>>>>
>>>
>>> So far, I see nothing yet preventing us from releasing
>>> this tomorrow... assuming that stays the same, I will
>>> move the files over to the main dist location to allow
>>> mirrors to start snagging and allow us a real release
>>> and announcement tomorrow.
>>>
>>
>
> 


Mime
View raw message