The followings tests of the testSuite are failing on Railo 4.0.3
On our end we have seen a bug using multipart/form-data to upload a file via CFHTTP by using Railo in the past. This issue isn't solved and may be related to the failing "can_upload_a_file". I've no idea why this file upload is not working on Railo but this bug is there since Railo 3.3.
Maybe you could see why this is not working, because I wasn't able to break down the error and we need this functionality in an actual project :(
I don't have a great Railo testing environment right now. I had originally been using the Jetty version, but Jetty doesn't support PUT/DELETE verbs, and I don't have time to futz around with Tomcat right now...
I've been working with Adam about the file upload using Railo (#89). It is working fine at our end but I must admit that we are using an old version of Taffy (1.0 with the upload fix on Railo 3.3).
I tried to update Taffy today but got an issue because I'm on Windows (#123). But once this is fixed, I'm prepared to make the test work with Railo.
@atuttle I'm still out there, was working on another projects
I've setup an environment with Railo 4 (4.0.4.001 on Tomcat) and checked the failing tests. Here is my feedback:
With the default setup, the custom status text is replaced by the standard status messages (OK, Not Found, ...).
To enable custom status messages, you need to add the line
to the file catalina.properties in the configuration directory of Tomcat
That said, I'm not big fan of using the status text to indicate an error to the client. I think it better to put the error message in the body of the response like it is done in the onError method.
They are failing because Railo is populating the form scope also on PUT requests, which ACF doesn't do. So you also get the fieldnames variable in the response. I fixed this on my side by changing the way the response is checked in the tests.
I fixed the test case on my side. The URL to call Taffy was not correctly generated and led to a 404 error.
Awesome, thanks for the feedback. I'll come back and revisit this soon.
I think this has been completely addressed, now. Closing!