OK guy\gals lets get this straight now, the default sandbox security
model(JDK 1.0/JDK 1.1)
implemented by NAV/IE as per specification is , "An applet can only open a
socket connection to the host from where it came from. By socket connection
I mean any socket level protocol like HTTP(HTTPUrlConn
David Harvill wrote:
> I have heard of an alternate solution, where the name of the host is
> passed to the applet as a parameter. I am not positive of the
> implementation since it is not my program. If the author doesn't mind, I
> will supply the source for this technique.
>
> -dave
How can t
I have heard of an alternate solution, where the name of the host is
passed to the applet as a parameter. I am not positive of the
implementation since it is not my program. If the author doesn't mind, I
will supply the source for this technique.
-dave
On Tue, 26 Jan 1999, Dimitris Vyzovitis w
>
>
> Yes, you are being blocked by Netscape's security manager. This is
> working as designed. An Applet is not allowed to open a socket with any
> host other that the host from which it was loaded.
In my experience netscape has a different point of view on security policy. I had a
similar
pr
Netscape lets you connect to the host were your applet is lodaded from only. To me it
looks, as
this is what you are doing. Only as the applet is on the local host you don't load it
via network
(www server) but directly from the disk. So Netscape calls your applet host
'local-classpath-classes'.
--- see bottom for my reply ---
On Tue, 26 Jan 1999, PAX! wrote:
>Hi all,
>
>I'm still developing my small application (I placed de question about
>printing a few days ago), and now I have another strange problem.
>
>I'm trying to connect via JDBC with a Postgres database. If I run with
>appletvi
