======
This webbug was originally closed as a duplicate of
4614560, but that assessment was incorrect. This
is the real bug.
======

There are 2 bugs in the JSSE code with regards to how it handles the
Plugin proxying. It may be too late for hopper (if the bug is escalated, we
stand a better chance). I'll see what I can do for mantis.

Background
==========
Mary (support) was contacted by Alventive, regarding a webbug that
they had filed. It was wrongly diagnosed as a duplicate of another
bug, and the duplicate was originally misfiled in the java_ssl category
(since closed). Anyway, I asked Mary to get more information, she came
back with the original submission (Problem #1), and the output of
-Djavax.net.debug=all which showed Problem #2.

The original submission thought it was a proxy authentication
problem. Problem #2 is definately auth-related, but I'm not
sure about #1.

Setup:
======

I was able to use Yingxian's squid proxy server
(http://www.squid-cache.org/), with basic authentication
turned on. I used javinator.sfbay:3128, username: ********
and password: ******** and used that to connect to http/https
servers on ports 80 (http) and 443 (https). Note, this server
only currently asks for authentication when connecting to
servers using these two port numbers.

I used JDK 1.4.0 FCS version. I never duplicated the
Problem #1, but looking at the traceback it's very
obvious what happened.

I had a simple little test applet (attached Get.tar),
then I used the following URL to
load the file and see the problem.

file:/path/to/files/Get.html

On summer I set up ClassFileServer, so it should
be fairly easy to set up to reproduce.


Problem #1:
===========

Here is the URL for the original webbug report:

http://webbugs.sfbay/rt/incidentDisplay?incidentID=143688

The incident is attached (incidentDisplay) in the attachment section.


Problem #2
==========

NullPointer when doing proxy authentication.

I asked them to run the bug with JSSE debugging turned on,
and we got back the following attachment (trace.txt), which
showed a slightly different error and traceback.


Overall
=======

While the bugs are somewhat related, they share the
same root cause which is that the setProxiedClient
is called, and then the subsequent code doesn't properly
check to see if the proxys have been set.

My initial evaluation in the evaluation section.

###@###.### 2002-06-06