logo



FAQ - MyUploader
Technical questions
  1. Where can I find a list of all error codes?
  2. I am getting a 100. What does this mean?
  3. I am getting a 302. What does this mean?
  4. I am getting a 401. What does this mean?
  5. I am getting a 404. What does this mean?
  6. I am getting a 500. What does this mean?
  7. Why can I not upload large files?
  8. How can I see the full HTTP response of my server?
  9. How can I resize images?
10. How can I create thumbnails?
11. How can I see thumbnails in the applet?
12. I miss my session. What can I do about that?
13. I miss my session in Internet Explorer and not in FireFox. What can I do about that?
14. How can I show a list of uploaded files?
15. How can I sent myself after an upload an email notification?
16. Does MyUploader have a log file?
17. Why am I getting the message 'Only basic authentication is supported'?
18. May I change the source code if I buy the Source Code Edition?
19. Can I remove the certificate?
20. Do I need to sign the applet if I change the source code?
21. Why don't I see the applet in Internet Explorer with Windows Vista or XP?
22. Does MyUploader has known issues?
23. My question is not listed.

General questions
1. Do I need to install Java on my Web Server?
2. Do I need to install additional software on my Web Server?
3. Why does MyUploader contains a trusted certificate?
4. Can I upload the files securely to the Web Server?
5. Does MyUploader support proxy authentication?
6. Does MyUploader have a resume feature?
7. Does MyUploader run in every browser?
8. Does MyUploader run on Linux or MAC desktops?
9. What is the expected EOL (End-of-Life) date?
10. My question is not listed.

Technical Questions

1. Where can I find a list of all error codes?
The error codes are http status codes. These codes are returned by the web server. See for a detailed description of all status codes: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html.

2. I am getting a 100. What does this mean?
The error code is an http status code. This code is returned by your server. 100 Means 'Continue'. You can get this response code when you are using the development server of Visual Studio. MyUploader uploads the files with the HTTP/1.0 protocol. In this protocol a response code 100 is not allowed. The 100 is part of the HTTP/1.1 protocol. The development server interprets however the upload request as an HTTP/1.1 request. Please use IIS in stead of the development server. With IIS the problem is solved.

3. I am getting a 302. What does this mean?
The error code is an http status code. This code is returned by your server. 302 Means 'Found'. See for a detailed description of all status codes: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html. One reason for this error can be that the server side code hasn't write permissions for the upload directory. Please check that the directory has write permissions.

Another cause for this error can be that the session cookie is not uploaded to the server. To solve this problem you need to enable cookies. To enable cookies you need to add the cookie parameter with Javascript to the applet tag. See example 4 for of the installation page.

4. I am getting a 401. What does this mean?
The error code is an http status code. This code is returned by your server. 401 Means 'Not authorized'. See for a detailed description of all status codes: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html. The reason for this error is that the session cookie is not uploaded to the server. To solve this problem you need to enable cookies. To enable cookies you need to add the cookie parameter with Javascript to the applet tag. See example 4 for of the installation page.

5. I am getting a 404. What does this mean?
The error code is an http status code. This code is returned by your server. 404 Means that the uploadURL can not be found on the server. Please check if your uploadURL is correct. See for a detailed description of all status codes: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html.

6. I am getting a 500. What does this mean?
The error code is an http status code. This code is returned by your server. 500 Means 'Internal Server Error'. In other words some error has occurred on your server. Please check the error log of your server for errors. One of the reasons can be that the upload directory cannot be found. The upload directory is called in the server side code '$base_directory'. Please check that this directory exists and the the server code has write permissions in this directory.

7. Why can I not upload large files?
For uploading large files you need to change some settings on the server. See the code examples for more information.

8. How can I see the full HTTP response of my server?
You need to add the parameter 'showHTTPResponse' to the html page, see: 'showHTTPResponse'. The response of the server will be logged in the Sun Java Console.
To start the console in Internet Explorer: Tools -> Sun Java Console.

9. How can I resize images?
Images can be resized with the applet parameter 'maxImageSize'. The resized images will be uploaded. Click here for more information.

10. How can I create thumbnails?
You can create thumbnails by resizing images. Images can be resized with the applet parameter 'maxImageSize'. Only the resized images (thumbnails) will be uploaded to the server. Click here for more information.

11. How can I see thumbnails in the applet?
To see thumbnails in the uploader you need to add the parameters 'showThumbNailsInApplet' and 'showThumbNailsInFileDialog' to the HTML page. When you select an image file in the uploader or in the file dialog you will see a thumbnail on right side. You only see the thumbnail when you have selected an image file. Click here for more information of the parameter 'showThumbNailsInApplet' and here for more information of the paramter 'showThumbNailsInFileDialog'. If you don't see the thumbnail fully in the uploader you need to increase the height of the applet. You can do that in the HTML page.

12. I miss my session. What can I do about that?
To use sessions you need to enable cookies. You can do this by adding the 'cookie' param with JavaScript to the applet tag. See for an example the README.txt file of the downloaded or purchased zip file.

13. I miss my session in Internet Explorer and not in FireFox. What can I do about that?
This problem can only occurr with IIS. Microsoft has slightly changed the cookie specification for security reasons. With this update scripting languages such as JavaScript can not access anymore the session cookie. Because MyUploader rely on JavaScript for reading the cookie the session will be lost. You can change this by disabling the Microsoft update. See: http://support.microsoft.com/kb/917412 for more information.

14. How can I show a list of uploaded files?
This functionality can be implemented in the server side code. See code examples.

15. How can I sent myself after an upload an email notification?
This functionality can be implemented in the server side code. See code examples.

16. Does MyUploader have a log file?
Yes, the log of the uploader can be found in the Sun Java Console. To start the console in Internet Explorer: Tools -> Sun Java Console

17. Why am I getting the message 'Only basic authentication is supported'?
You are using a proxy server with an authentication scheme other than 'basic authentication'. MyUploader supports only 'basic authentication'.

18. May I change the source code if I buy the Source Code Edition?
Yes, you may change the source code. If you change the code you need to resign the binary code.

19. Can I remove the certificate?
You can not remove the certificate because only signed applets are allowed to read files from the file system.

20. Do I need to sign the applet if I change the source code?
Yes, if you change the source code you need to sign the applet. For signing the applet you need to have a code sign certificate. You can use a self signed certificate or you can buy one from Thawte. The difference between the two is that with a self-signed certificate the user can see that the certificate is not trusted. For creating a self-signed certificate you need to use the Keytool of the JDK. For signing the applet you need to use the JarSigner of the JDK.

21. Why don't I see the applet in Internet Explorer with Windows Vista or XP?
The examples on JavaAtWork uses the 'applet' tag for installing the applet. Regarding SUN this is preferred way to install the applet for an internet environment. The SUN Java Plugin uses the 'applet' tag. Internet Explorer comes with an embedded Java Plugin. This plugin uses the 'object' tag instead of the 'applet' tag. If the SUN Java Plugin is not installed than you need to use the 'object' tag. The 'object' tag is not supported by other browsers. Therefore the preferred way in this situation is to use a combination of the 'object', 'embed' and the 'applet' tag. Click here for an example.

22. Does MyUploader has known issues?
See for the known issues the details page.

23. My question is not listed.
If your question is not listed please contact JavaAtWork.

General Questions

1. Do I need to install Java on my Web Server?
No, MyUploader runs in the browser of the client and therefore there's no need to install Java on the Web Server.

2. Do I need to install additional software on my Web Server?
Yes, you need to install a server side component for storing the files on the server. This server side component can be written in: ASP, ASP.NET, Coldfusion, Java or PHP. See here for example code for the server implementation.

3. Why does MyUploader contains a trusted certificate?
MyUploader contains a certificate for reading the local files on the file system. Only signed applets are allowed to access the local file system.

4. Can I upload the files securely to the Web Server?
Yes you can. Files are uploaded securely with the https protocol. This means that the files are encrypted during transmission. To enable https you must install a SSL certificate on your Web Server from a Certificate Authorithy e.g. Thawte.

5. Does MyUploader support proxy authentication?
Yes, MyUploader supports basic proxy authentication only so it will not work e.g. with Microsoft proxies that do authentication through NTLM.

6. Does MyUploader have a resume feature?
No, MyUploader doesn't have a resume feature.

7. Does MyUploader run in every browser?
MyUploader runs in every browser where the JDK 1.4 plugin (or a newer version) is installed. The browser must support the full Applet API. MyUploader is tested on Internet Explorer and Firefox. Note that the drag-and-drop functionality doesn't work anymore on Mac OSX with the latest OSX updates. See the 'Known Issues' on the details page for more information.

8. Does MyUploader run on Linux or MAC desktops?
Yes, MyUploader is written in Java. Java is a platform-independent programming language. Therefore MyUploader runs on every platform where JDK 1.4 plugin (or a newer version) is installed.

9. What is the expected EOL (End-of-Life) date?
The expected EOL (End-of-Life) date of MyUploader is January 1, 2015 2016. After this date no new versions or certificate renewals will be released.

10. My question is not listed.
If your question is not listed please contact JavaAtWork.

dot