Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:7613
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 5 Feb 2004 14:27:33 +0200 (EET)
Reply-To: Jani Taskinen <sniper@iki.fi>
To: Doru Petrescu <pdoru@kappa.ro>
Cc: internals@lists.php.net
In-Reply-To: <1075974111.3098.59.camel@dtp.kappa.ro>
Message-ID: <Pine.LNX.4.53.0402051427070.22605@ybpnyubfg.ybpnyqbznva>
References: <1075974111.3098.59.camel@dtp.kappa.ro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] apache2 sapi uninitialized content-length value
From: sniper@iki.fi (Jani Taskinen)


    I don't remember seeing any patch..nor do I see one now..
    And what exactly is the problem you see that the patch fixes?
    
    --Jani
    

On Thu, 5 Feb 2004, Doru Petrescu wrote:

>
>
>Hi,
>
>some time ago I sent a patch to fix this uninitialized variable in the
>apache2 sapi code. all other SAPIs DO initialize it, so I figured out it
>is something that should be corrected. 
>
>I see neither php-5.0.0B3 nor php-4.3.5RC2 implement this.
>
>Can someone comment on this ? Was my 2 line patch incorrectly wrote ?
>Maybe it did not apply ? Maybe it is wrong to initialize that variable ?
>but then why other SAPIs initialize it ? are them wrong ? is there a
>hidden security problem that I did not see ?
>
>My original email was sent on 20 Nov 2003, original subj was "[PHP-DEV]
>[PATCH] sapi apache2 uninitialized content-length value"
>
>
>