FAQ/Known Issues

Known Limitations

SlickUpload enables features based on browser support

SlickUpload doesn't use any ActiveX/Flash/Java plugins, so the functionality on a given browser is limited to what that browser supports. Firefox 3.6+ and Chrome 8+ support multiple file selection. Chrome 11+ supports folder selection. IE only supports single file selection up to version 9. MS is adding support for multiple file selection to IE 10, so SlickUpload will support that when IE 10 is released.

iOS doesn't support uploading

Mobile Safari doesn't support uploads, so users will receive the message contained in the Unsupported template.

SlickUpload cannot select files without user interaction

Because of security concerns and restrictions implemented by the browser, SlickUpload cannot select files without user interaction. It also cannot invoke the file selection dialog through code -- the user must click on the file or folder selector to pop up the file selection dialog.

ASP.NET application wide tracing disables SlickUpload

Because of the way application wide ASP.NET Tracing integrates in the ASP.NET pipeline, it reads in the upload body before SlickUpload can access it. This means that if <trace enabled="true"> is set in the web.config, SlickUpload won't be able to receive or process the upload requests. You can still use per page tracing (configured in the <%@ Page %> directive).

SlickUpload is limited by the maximum request size supported by IIS

Because SlickUpload is a browser component, it uses standard non-chunked uploads. This means that it can upload files only up to the maximum request size supported by IIS. See the following matrix:

IIS Version	Max Request Length
IIS 5	2 GB
IIS 6	4 GB
IIS 7 Classic Mode	4 GB
IIS 7 Integrated Mode	2 GB
VS.NET integrated WebDev server	2 GB