|
FAQ - MyUploader
|
|
Technical questions
|
|
1.
|
|
2.
|
|
3.
|
|
4.
|
|
5.
|
|
6.
|
|
7.
|
|
8.
|
|
9.
|
|
10.
|
|
11.
|
|
12.
|
|
13.
|
|
14.
|
|
15.
|
|
16.
|
|
17.
|
|
18.
|
General questions
|
|
1.
|
|
2.
|
|
3.
|
|
4.
|
|
5.
|
|
6.
|
|
7.
|
|
8.
|
Known problems
|
|
1.
|
|
2.
|
|
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 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.
|
3. 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.
|
4. 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.
|
5. 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. |
6. 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.
|
7. 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.
|
8. 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.
|
9. 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.
|
10. How can I show a list of uploaded files? |
|
In the 'upload.php' the file names of the uploaded files can be stored in the session of the user. In the 'success.php' script
the names can be extracted out of the session and be listed on the success page. Click here to see an example in PHP.
|
11. How can I sent myself after an upload an email notification? |
|
This functionality can be implemented in the server side code.
Click here to see an example in PHP.
|
12. Does MyUploader has 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
|
13. 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'.
|
14. 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.
|
15. Can I remove the certificate? |
|
You can not remove the certificate because only signed applets are allowed to read files from the file system.
|
16. 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.
|
17. 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.
|
18. 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 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.
|
7. 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.
|
8. My question is not listed. |
|
If your question is not listed please contact JavaAtWork.
|
Known issues
|
1. MyUploader Form Add-On doesn't work in Opera |
|
MyUploader Form Add-On doesn't work in Opera. The Add-On uses the Java Common Dom API. This API is not fully supported In Opera.
The user will see an error message when the Add-On is used in Opera. Only the Form Add-On doesn't work in Opera, MyUploader works perfect.
|
2. MyUploader Form Add-On cannot validate form fields. |
|
MyUploader Form Add-On cannot invoke JavaScript methods. For this reason form validation with JavaScript is not possible.
|
