FileSender

FileSender 1.1 contains a number of known issues that we were unable to fix before releasing.  These issues typically are a consequence of certain architectural decisions or deficiencies in technology we depend on.  The majority of these issues are annoying but not show stopping.  

1. In the same browser session, when downloading the same file more than once using the same url or directly from the MyFiles table the download email notifications are only generated for the first download.  See bug ticket #356.
2. The subject and message fields do not clear after cancelling an upload if a user authenticated using an upload invitation voucher.  The fields do get properly cleared when using standard authentication.  See bug ticket #357.
3. UTF8: when downloading a filename with international characters other than ISO-8859-1 it will look 'funny' but fully usable when downloaded with IE.  See bug ticket #374
4. When a user starts downloading a file, and then cancels the download, a "user has downloaded the file" email is still generated.  See bug ticket #307
5. When a user has downloaded a file, the download page is accessible until the user's local browser cache is cleared or the file is deleted on the FileSender server.  This is a consequence of the choice to rely on a unique URL for authenticating users to downloads.  See bug ticket #187.
6. 'My Files' listing and Bcc issues when uploading using a voucher and being authenticated as another user than the voucher issuer. See bug tickets #553 and #554.
7. Problematic downloads using Chrome on Windows7-without-SP1.  See bug ticket #588.