Yes. This was a change introduced with 4.0.1. Actually, in the 4.0 server, there was no limit. 4.0.1 added a limit to provide a means to protect the server. We will add a note somewhere to help to identify this change, and the configuration file impact that may be required.
The read timeout configuration value is used to cap the time that the server will allow reading the entire request. So, just as you describe, you need to consider how large of a request that you will allow your server to accept, and the max time that the input of such a request could require. In your example, I would suggest that you increase this timeout to at least 60 seconds. Bas Scheffers wrote on 2/18/2004, 4:31 AM: > Hi Mark, > > Mark Page said: > > There is a configurable maximum upload size limit. This defaults to > 1MB. > I knew it must have been something like that! Did the default change from > 4.0 to 4.01? I am using the same nsd.tcl as I did before the upgrade. > > > Note, you might need to examine the read timeout value specified. This > Does this determine how long the upload can take? I will probably have to > bump this up, even if my users are clued up enough to follow my > instructions (ie: max 600 pixels and 100Kb file size), if they use a 56K > modem (upload = 28.8) it will still take at least 27 seconds! > > Thanks, > Bas. > > > -- > 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. -- 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.
