Status: 
Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 18 Jun 2001 11:40:58 -0700
From: Jim Winstead <jimw@trainedmonkey.com>
To: apreq-dev@httpd.apache.org
Subject: Re: libapreq 0.32 ready yet?
Message-ID: <20010618114058.A20473@trainedmonkey.com>
Mail-Followup-To: apreq-dev@httpd.apache.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010618113714.A16822@trainedmonkey.com>
User-Agent: Mutt/1.3.18i

duh, don't mind me. it does work in 0.31, and the code looks intact
for 0.33.  (there's a second check in ApacheRequest_parse_multipart
that i didn't quite get to. :)

jim

On Mon, Jun 18, 2001 at 11:37:14AM -0700, Jim Winstead wrote:
> On Mon, Jun 18, 2001 at 11:28:49AM -0700, Doug MacEachern wrote:
> > On Mon, 18 Jun 2001, Jim Winstead wrote:
> >  
> > > but are you sure it worked before? i don't see any code in 0.31 to
> > > actually implement the POST_MAX handling.
> > 
> > % grep -i post_max Request/Request.xs
> >             if (strcaseEQ(key, "post_max")) {
> >                 RETVAL->post_max = (int)SvIV(ST(i+1));
> 
> d'oh! you'd think i would have looked for it in lowercase. :)
> 
> it looks to me like this code only gets used for regular post data,
> and not file uploads. it looks to me like this was true in 0.31, too.
> 
> jim