On 2004.10.27, Bernd Eidenschink <[EMAIL PROTECTED]> wrote: > > in the context of Khy's question: Is it safe to say: > Always set both "maxpost" and "maxinput" to the same values? > Or else there are any side effects...? > > Is "maxpost" still relevant? It's still in the code, but in > what way does it affect "postings"?
I'd have to look at the code to see if this is actually /true/ but my recollection is that "maxinput" covers the entire HTTP request (incl. the headers, which contain the cookie data, etc.) while "maxpost" only talks about the HTTP request body size. maxinput < maxpost doesn't make sense, but setting maxinput > maxpost does. Setting maxinput = maxpost is probably okay in most situations, though. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
