Hello Clayton, Thank you for the suggestion. I noticed in the thread I referenced earlier ( http://active4d.2283328.n4.nabble.com/Large-File-Uploads-td2958943.html#none ), this was also suggested. However, Aparajita said "There is no need to do this, as Active4D automatically calls this command with the value set in Active4D.ini."
But, perhaps that's the problem? If Active4D is setting the 4D Web Server limit to whatever I set, and exceeding this limit causes a connection reset instead of a proper response.. well, that seems to be the situation I'm in. Can predictably I set the database parameter to a higher value after Active4D has set it to the INI file value? Your comments below imply this is the case, but if Active4D can change the setting at any time I'd be afraid of random breakage. I suppose I could always make the limit huge in Active4D, check the filesize in my script, and return a 413 manually. That doesn't seem ideal though. I'll do some experimenting, thanks. Chris Backas Bristol Capital, Inc. On Feb 11, 2011, at 8:25 AM, Donahue, Clayton L. wrote: > Hi Chris > > I *think* we've had a similar issue in the past. Aparajita's right > in that the problem lies in 4D's web server. We solved our issue > using the "Maximum Web requests size" database parameter, which we > set during our database initialization code. Here is the code and > comments I have: > > [code] > // > = > = > = > = > = > = > = > = > = > = > ====================================================================== > // Active4D provides (via the Active4D.ini file) the ability to > "cap" the max upload size of a document. If the > // document exceeds this size, a status "413 Entity too Large" is > supposed to be thrown. However, if the > // document's size is greater than the .ini file cap, but very > close to (though not exceeding) 4D's max > // request size, a status 200 is returned, but a "Connection with > Server has been reset" message is > // displayed. So, the solution is to increase 4D Server's max > request size, but still cap the limit in > // Active4D. We will set it to 8 MB. This causes the 413 to be > sent, which we can trap for. > // > = > = > = > = > = > = > = > = > = > = > ====================================================================== > SET DATABASE PARAMETER(Maximum Web requests size;8000000) > [/code] > > For the record, we have our "maximum request size" set to 5MB in the > Active4D.ini file. > > Hope this helps, > - Clayton Donahue > > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev > Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ CONFIDENTIALITY NOTICE: This email (and any related attachments) contains information from InfoPlus (a service of Bristol Capital, Inc.). It is intended only for the addressee and may contain information that is confidential and/or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or are acting as agent for the intended recipient, any use or disclosure of this communication is prohibited. If you have received this communication in error, please notify me immediately to arrange for the appropriate method of returning or disposing of the communication. If our respective Companies have confidentiality provisions in effect, this email and the materials contained herein are deemed CONFIDENTIAL and should be treated accordingly unless expressly provided otherwise. _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
