B
brianlafertewk
Guest
I have simple file uploader that posts via a HTML form as multipart/form-data. The receiving WebSpeed code simply does a get-value() to get the file name, and a get-binary-data() to get the actual file contents into a MEMPTR, and then write the results out under a new file name. Simple and easy, working for years. Running this code under PASOE the code fails. I see the incoming file being written into the a directory (the working directory) as a 0 byte file. The MEMPTR value returns null (either comparing it to ? or doing a GET-SIZE(m)). Using Classic WebSpeed the same code returns a MEMPTR with the actual file, and the correct size, and it can be written to disk (or wherever) from there. In PASOE I have binaryUploadMaxSize for the ABL application in question set to a high value, so it's not a limit there. The knowledge base seems to indicate this is the only setting needed to enable binary uploading using the compatibility handler. Is there something else that needs to be done to support basic binary uploads with classic WebSpeed code under PASOE? This is under 11.7.2. Thanks, Brian
Continue reading...
Continue reading...