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/
