Re: raise POST_MAX after instantiation

On Oct 19, 2006, at 4:18 AM, Philip M. Gollucci wrote:
> http://www.mail-archive.com/[email protected]/msg00716.html
>
> Does that help ?

unfortunately not... all those approaches give me the 'Conflicting  
Information' message that everything else i tried did

I think the issue is entirely because I cause a parse via a ->param  
call on my apreq stash very early on in apache, usually either:
	on a cookie check handler, before the main handler
	right on the line or so of my main handler, as i create a context  
object for my dispatch

i think that once , upon a time, there was information on the docs  
that this was impossible

in any event, after parse is called -- either explicitly or  
implicitly by accessing param/args -- i think it may be impossible to  
make a new apache2::request object that is tied to the  
apache2:requestrec , or raise/lower the post_max/readlimit

for now, i've got an array of regexes for pages that get higher  
post_max/readlimit, and i create my initial post_max  based on  
whether or not the uri matches to an element in the list

gets the job done, but its dirty dirty dirty


// Jonathan Vanasco

| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -