I believe the issue he's referring to is happening when trying to
retrieve large files from the server, and not an issue with trying to
post a large amount of data. I'm actually seeing the same issue as well
when trying to fetch a large file, and am in the middle of trying to
debug further.
When dealing with sending data to the server, however, there are two
configuration options that come into play:
1. The "maxinput" parameter, which is the one you mentioned, is the
maximum size for the request and headers. By default this is set to be ~1M.
2. The new "ns_limits -maxupload" parameter, which is the maximum size
allowed for the content portion of the request. An example would be a
the content-length for a file upload. The default for this is ~10M.
server1:nscp 1> ns_limits list
default
server1:nscp 2> ns_limits get default
nrunning 0 nwaiting 0 ntimeout 0 ndropped 0 noverflow 0 maxwait 100
maxupload 10240000 timeout 60 maxrun 100
So when a request is received, the server first consumes, and parses,
the request and headers (checking "maxinput"), then reads the rest of
the content (checking "maxupload").
Hope that helps!
- n
[EMAIL PROTECTED] wrote:
On 6/1/06, Hérick Moniz <[EMAIL PROTECTED]> wrote:
I got a strange bug with aolserver on the latest version of Mac OS X,
on PPC or Intel. Everything compile fine, with gcc4 or gcc 3.3, and
the software seems to run fine but I am not able to transfer file
larger then 100 Kb. The transfer start but stop without any error or
warning.
Have you set the 'maxinput' parameter in nssock?
http://www.mail-archive.com/aolserver@listserv.aol.com/msg08208.html
Vinod
--
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.
