where is the documentation that there was a "known issue" with multi-part form parsing in updater 3? Just wondering...
thanks, Dave >>> [EMAIL PROTECTED] 09/20/04 1:34 PM >>> Many of us (including yours truely) have been getting the HTTP 500 error when uploading files using HTML forms (while using CFMX). I have spent a lot of time researching this (too much in fact). Below is a summary of the results from my research. The error is a known issue in "Jrun 4 Updater 3" and a fix is available from MM (just not for CFMX as of yet). Please feel free to comment. And let me know if I am incorrect in any of my statements or research. =========== Okay. From what I have discovered this particular 500 error (as well as a few others) are known issues with "JRun 4 Updater 3" (currently this is the version used in CFMX6.1). A few days ago Macromedia released "JRun 4 Updater 4" for Jrun 4 only (14 days after "CF6.1 Updater 1" was released. The CF6.1 Updater 1 still uses "JRun 4 Updater 3"). The official "JRun 4 Updater 4" includes the fixes for the all-too-common 500 error(s) (there are several). So my question: How do we CF developers not using the full version of Jrun 4 get the "Jrun 4 Updater 4" specific fixes into CFMX? And why couldn't MM wait the additional 14 days before releasing "CF6.1 Updater 1" so that they could include the "JRun 4 Updater 4" in it? Note to all you JRun 4 users: MM has not yet released any documentation regarding all of their fixes in the "JRun 4 Updater 4". Because many programmers like ourselves are worried about code updates overlapping it is suggested to run "CF6.1 Updater 1" before "JRun 4 Updater 4". So far a couple people have tried doing the oposite to see the results (including testing it with Backstone Beta1) and have not had any errors. But until MM releases more information it is suggested to do it in this manner. -Jeff C note: To see the generic "JRun Servlet Error" do the following... Next time you get the 500 error don't restart CF just yet. In Internet Explorer go to "Tools->Internet Options-->Advanced (tab)" and disable "Show friendly HTTP error messages". Then make the error happen again. Now view the source (right-click in IE window that has the error. Choose View Source). Then you'll see the generic "JRun Servlet Error". you can thank IE for misleading us on that one =\ --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
