Question
Multi-part forms and server-side redirects
Hello all you wonderful CF people. There is already a topic
about this, but we're still a bit stumped. In most of our testing
we are using the development version of CF8.01 (8,0,1,195765) and
the built in web-server on Windows XP. We have also tried it on a
local development server on Windows 2003. We have a form that uses
the encoding type "multipart/form-data". After the form is posted
and any files are uploaded, we do a server-side redirect using
Fusebox's 'relocate' verb. This uses PageContext.forward() "behind
the scenes".
When we run this application on CF8 and post the form, we get a "Corrupt form data: premature ending" error message in the browser. This appears to be a known bug (according to one Adobe forum thread), but I can't find a bug record anywhere on the Adobe site about it. The one thread indicated that it was fixed in CF version 8.01, but we're still seeing the problem even after updating.
We know about the jvm adjustment (coldfusion.markResetForMultiPart) that makes the CF8 uploading functionality work like CF7, but we would very much like to take advantage of the new uploading power of CF8. We can decrease our use of server-side redirects, but there are a few cases where removing the server-side redirect isn't very plausible.
Anyone have any suggestions? Does anyone know where to track this bug, if it is indeed already listed somewhere? Thanks in advance.
T
When we run this application on CF8 and post the form, we get a "Corrupt form data: premature ending" error message in the browser. This appears to be a known bug (according to one Adobe forum thread), but I can't find a bug record anywhere on the Adobe site about it. The one thread indicated that it was fixed in CF version 8.01, but we're still seeing the problem even after updating.
We know about the jvm adjustment (coldfusion.markResetForMultiPart) that makes the CF8 uploading functionality work like CF7, but we would very much like to take advantage of the new uploading power of CF8. We can decrease our use of server-side redirects, but there are a few cases where removing the server-side redirect isn't very plausible.
Anyone have any suggestions? Does anyone know where to track this bug, if it is indeed already listed somewhere? Thanks in advance.
T
