You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Jonathan <ap...@2xlp.com> on 2006/10/19 08:13:38 UTC

raise POST_MAX after instantiation

I have POST_MAX set at 10k when i instantiate an apache2::request  
object and stash it in a context object at the start of my modperl  
handler

annoyingly, i've run into a situation where a single page needs ~50k  
of post data

what is the standard method for dealing with that? i think the only  
way to deal with this might be trying to figure out if i'm  
dispatching to the 'fat' page before i instantiate the request  
object.  am i right?

Re: raise POST_MAX after instantiation

Posted by Jonathan <ap...@2xlp.com>.
On Oct 19, 2006, at 4:18 AM, Philip M. Gollucci wrote:
> http://www.mail-archive.com/apreq-dev@httpd.apache.org/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
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -



Re: raise POST_MAX after instantiation

Posted by "Philip M. Gollucci" <pg...@p6m7g8.com>.
this one time in band camp Jonathan said on 10/18/06 23:13:
> 
> I have POST_MAX set at 10k when i instantiate an apache2::request object 
> and stash it in a context object at the start of my modperl handler
> 
> annoyingly, i've run into a situation where a single page needs ~50k of 
> post data
> 
> what is the standard method for dealing with that? i think the only way 
> to deal with this might be trying to figure out if i'm dispatching to 
> the 'fat' page before i instantiate the request object.  am i right?
http://www.mail-archive.com/apreq-dev@httpd.apache.org/msg00716.html

Does that help ?


-- 
------------------------------------------------------------------------
Philip M. Gollucci (pgollucci@p6m7g8.com) 323.219.4708
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior Software Engineer - TicketMaster - http://ticketmaster.com
1024D/A79997FA F357 0FDD 2301 6296 690F  6A47 D55A 7172 A799 97F

When I call your name, Girl, it starts to flame
Burning in my heart, Tearing it all apart..
No matter how I try My love I cannot hide....