Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Using proxy parameter for DriverManager.getConnection() calls

2 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-05-20 20:22:13.0Z
Edward Bauer Posted on 1997-05-06 13:58:06.0Z
Message-ID: <336F38EE.1D9B@stsci.edu>
Date: Tue, 06 May 1997 09:58:06 -0400
From: Edward Bauer <bauer@stsci.edu>
X-Mailer: Mozilla 3.01 (X11; I; SunOS 5.5 sun4m)
MIME-Version: 1.0
Subject: Using proxy parameter for DriverManager.getConnection() calls
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 24
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:871
Article PK: 252623

I have a simple applet that is served via the HTTP server that comes
with jConnect. The server is running under Solaris.

Originally, I had that applet make connections with this form
of the getConnection() call:

DriverManager.getConnection(url, user, password);

This worked great if I was running Netscape on one of the machines in
our company domain and accessing this applet. That applet connects to
the Sybase internet-accessible pubs2 database, some local databases,
etc.

I tried to access the applet from a Netscape browser running off-site
and the getConnection call would fail with a security exception. Once I
modified the call to use a Java Properties list and passed the proxy
data in addition to username and password, it worked fine from the
remote location.

Any idea what made it work without the proxy in one case and yet require
it in other cases?

Thanks alot,

Ted


David Clegg Posted on 1997-05-20 20:22:13.0Z
Message-ID: <338207F5.644E3979@sybase.com>
Date: Tue, 20 May 1997 13:22:13 -0700
From: David Clegg <davec@sybase.com>
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.2.13 i586)
MIME-Version: 1.0
To: Edward Bauer <bauer@stsci.edu>
Subject: Re: Using proxy parameter for DriverManager.getConnection() calls
References: <336F38EE.1D9B@stsci.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 35
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:810
Article PK: 252562

I would guess that in the case that worked, the Database you connected
to was running on the same machine as the web-server you used to
download the java classes from (or you used the file:... URL to
load the classes locally). In the Internet case the Security violation
was raised for trying to open a connection to a machine other than
the one which the class files were downloaded from.

dave

>
> I have a simple applet that is served via the HTTP server that comes
> with jConnect. The server is running under Solaris.
>
> Originally, I had that applet make connections with this form
> of the getConnection() call:
>
> DriverManager.getConnection(url, user, password);
>
> This worked great if I was running Netscape on one of the machines in
> our company domain and accessing this applet. That applet connects to
> the Sybase internet-accessible pubs2 database, some local databases,
> etc.
>
> I tried to access the applet from a Netscape browser running off-site
> and the getConnection call would fail with a security exception. Once I
> modified the call to use a Java Properties list and passed the proxy
> data in addition to username and password, it worked fine from the
> remote location.
>
> Any idea what made it work without the proxy in one case and yet require
> it in other cases?
>
> Thanks alot,
>
> Ted