When using any new program for the first time it is easy
to make errors, and those errors can still be delivered
even though they have since been corrected, from caching
by either your web browser or your ISP. Caching is
performed by your web browser to conserve downloads by
storing a copy in a Temporary Internet folder or "cache".
Caching is also performed by ISPs to conserve their data
costs. Pages downloaded by their users are stored by proxy
servers or in caching engines so that they can be
delivered internally (from within their own network) and
thus save the data cost. Some ISPs will enforce caching
Artists and designers need to be aware of this phenomenon because editing a web site can be frustrating if one cannot see the updated pages, but instead see the old pages.
Still getting the same error even though you have made corrections? On refresh you may be getting the latest page in your browser, but not the latest image.class file. This can be due to caching of previous errors by either your browser or your ISP. You can alter your browser settings for refresh, but some proxy connections may not update for days.
When reloading the page, try holding down the "Shift" key at the same time. If this fails then to avoid cached errors you will need to use a different image file name. Renaming the image.class file and modifying the applet's image parameter will save encrypting a new image.
Java 1.6 has affected the use of encryptions for "multiple
sites" which create a domain lock file instead of encrypting
the designated key into the image. A workaround is adding
.dat to the server's Mimetypes list as ( .dat - plain/text
). However this not recommended as visitors will then be
able to download your registration file.
Return to top