can you go to where you have the personal server while it is running and check for a folder \ode2
--
You received this message because you are subscribed to a topic in the Google Groups "App Inventor for All" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ai4a/pqy4NsIPl0E/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to ai4a+uns...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
To unsubscribe from this group and all its topics, send an email to ai4a+unsubscribe@googlegroups.com.
In this release, low
and custom
settings are removed from the Java Control Panel(JCP)'s Security Slider.
Depending on the security level set in the Java Control Panel and the user's version of the JRE, self-signed or unsigned applications might not be allowed to run. The default setting of High permits all but local applets to run on a secure JRE. If the user is running an insecure JRE, only applications that are signed with a certificate issued by a recognized certificate authority are allowed to run.
For more information, see the Security section of the Java Control Panel documentation.
As of JDK 7u21, JavaScript code that calls code within a privileged applet is treated as mixed code and warning dialogs are raised if the signed JAR files are not tagged with the Trusted-Library attribute.
For more information, see Mixing Privileged Code and Sandbox Code documentation.
The JDK 7u21 release enables users to make more informed decisions before running Rich Internet Applications (RIAs) by prompting users for permissions before an RIA is run. These permission dialogs include information on the certificate used to sign the application, the location of the application, and the level of access that the application requests. For more information, see User Acceptance of RIAs.
Starting from JDK 7u21, it is recommended that all applications be signed. In addition, it is also possible to restrict signed applications to the security sandbox.
Therefore, the previous use of the term "unsigned"
to mean an application that ran in the security sandbox and "signed"
to mean an application that ran with extended permissions, is no longer meaningful.
The terminology in the Java Tutorial and the Java SE Guides has been changed to use "sandbox application" for applications that are restricted to the security sandbox, and "privileged application" for applications that have extended permissions.
Unsigned or self-signed applications may not be supported in future JDK update releases.
For more information on signing applications, see Understanding Signing and Verification. Deploying with Applet Tag describes setting permissions for an applet within the applet tag.
--
You received this message because you are subscribed to the Google Groups "App Inventor for All" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ai4a+uns...@googlegroups.com.
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Modified appinventor/appengine/src/com/google/appinventor/server/util/CacheHeadersImpl.javadiff --git a/appinventor/appengine/src/com/google/appinventor/server/util/CacheHeadersImpl.java b/appinventor/appengine/src/com/google/appinventor/server/util/CacheHeadersImpl.javaindex 0e63832..233d7ca 100644--- a/appinventor/appengine/src/com/google/appinventor/server/util/CacheHeadersImpl.java+++ b/appinventor/appengine/src/com/google/appinventor/server/util/CacheHeadersImpl.java@@ -21,7 +21,7 @@ public class CacheHeadersImpl implements CacheHeaders {@Overridepublic void setNotCacheable(HttpServletResponse resp) {- resp.setHeader("Cache-Control","no-cache, no-store, max-age=0, must-revalidate");+ // BREAKS WEBSTART in JAVA1.7u21 resp.setHeader("Cache-Control","no-cache, no-store, max-age=0, must-revalidate");resp.setHeader("Pragma", "no-cache");resp.setHeader("Expires", TIME_IN_THE_PAST);}