need help Connect failure in an applet

An applet is only permitted to connect back to the originating server
IP that served the HTTP request. If you try to connect to a different
address, it will fail with a permissions exception. 127.0.0.1 is the
localhost loopback address, and would not work from a remote host
either.

Alex Turner
NetEconomist

Alex,

Immediately after sending the inquiry I discovered that default applet
behavior is as you desribe and that one must change the java.policy file to
allow the connection.

When I did that, I now get a different error, that the postmaster is
refusingthe connection. The solution to this problem is supposed to be
adding tcpip_socket = true to the postgresql.conf file and restarting the
postgresql service. When I did that, I got an error when restarting the
service.

Now I am rebooting to see if that helps.

Jay

-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org]On Behalf Of Alex Turner
Sent: Friday, January 07, 2005 12:04 PM
To: jdoggett@markem.com
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] need help Connect failure in an applet

An applet is only permitted to connect back to the originating server
IP that served the HTTP request. If you try to connect to a different
address, it will fail with a permissions exception. 127.0.0.1 is the
localhost loopback address, and would not work from a remote host
either.

Alex Turner
NetEconomist

On Fri, 7 Jan 2005 11:23:46 -0500, John Doggett <jdoggett@markem.com> wrote:

Does anyone know why a connect call will fail with an
AccessControlException:access denied(java.net.SocketPermission
127.0.0.1:5432 connect, resolve) from a browser delivered applet?

The applet works fine in the debugger.

I have PostgreSQL running in windows.

Jay

This e-mail message and any attachments are confidential and may be
privileged. If you are not the intended recipient, please notify MARKEM
Corporation immediately -- by replying to this message or by sending an
e-mail to helpdesk@markem.com -- and destroy all copies of this message
and any attachments. Thank you.

Nothing contained within this e-mail, including attachments, is intended

to

include or constitute an "electronic signature" as defined in 15 U.S.C. �
7006(5).

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

-------------
This message has been scanned for malicious code and inappropriate content.
If you feel this message should have been blocked, please forward to
abuse@markem.com.

On Fri, 2005-01-07 at 13:03 -0500, John Doggett wrote:

When I did that, I now get a different error, that the postmaster is
refusingthe connection. The solution to this problem is supposed to be
adding tcpip_socket = true to the postgresql.conf file and restarting the
postgresql service. When I did that, I got an error when restarting the
service.

If you are using 8.0, you should instead look at the listen_addresses
configuration. (I understand that tcpip_socket is not used any more)

Note that I have not tried 8.0 yet myself, so this could just be
hallucinations on my part.

gnari