It could be that the request body is taking a long time to parse the
uploaded file looking for the various multi-part areas.
I have had no problems in uploading large files, but i would caution
that your front-end web server might be timing out the request before it
all completes. nginx for example has a very low number of minutes as a
default as a defense against denial-of-service attacks.
incidentally i am pretty sure we don't support the requesttimeout
property -- unless one of my other team members added that in and i
wasn't aware.
Magnus wrote:
I have a bug that I have been trying to solve for a little while and
haven't been able to figure out. The pages in question involve
uploading large audio files (sometimes up to 100MB) which means it
takes a a long time to process. A long time ago I added a URL
requesttimout = 300 to the form's action URL. The form itself has 6
fields in addition to the File upload field.
Every now and again users encounter an error that always hits at the
same line of code. What is odd is that the only FORM field that shows
up in the DUMP in the error email I get is the file upload field. This
has mystified me since there is no situation where just the file
upload field is sent.
Could it be the request timeout that could causes this? Is the file
field sent first and this the only field the server know about when
the request is timed out?
I added to request timeout to try to make sure the request had enough
time to do the upload but am I using it backwards and causing a
problem rather than solving.?
Thanks for your help.
Magnus
--
tag/function ref: http://www.openbluedragon.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
