Bordermanager proxy authentication re-direction fails with Chimera

RESOLVED WONTFIX

Status

Camino Graveyard
General
RESOLVED WONTFIX
15 years ago
13 years ago

People

(Reporter: John Endahl, Assigned: Mike Pinkerton (not reading bugmail))

Tracking

unspecified
Camino1.5
PowerPC
Mac OS X

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20021220 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20021220 Chimera/0.6+

We use Novell's Bordermanager for web proxy in our school district. It uses an
SSL connection for authentication, prompting the user for a username and
password. Chimera does not work properly with the re-direct, it typically gives
a "Document contains no data" error and the login screen does not appear. I do
see that Chimera is trying to contact the proxy server during the re-direct, but
 it does not connect.

I am using Chimera build 2002122004.

Netscape 7.01 works properly with the re-direct.
So does Mozilla, build 2002121216

Reproducible: Always

Steps to Reproduce:
1. Open Chimera
2. Enter a URL
3. Wait for the error message

Actual Results:  
Nothing. The status bar indicates Chimera is trying to contact the proxy server,
but the login screen does not appear

Expected Results:  
An SSL login screen should appear, giving users the opportunity to enter their
password and username.

Comment 1

15 years ago
John, is this still a problem with recent Camino Nightlies?
(Reporter)

Comment 2

15 years ago
Chris,

There has been some change, but it is still an issue.

When I start Camino (20033030613), it will typically time out with the "Page
contains no data" error message. If I attempt to reload the page, after the
fourth or fifth attempt, it will usually properly re-direct and show the
authentication screen. I can log on and browse normally. Our BMgr proxy is set
to require re-authentication if the browser is idle for four minutes. I have
only had one time when the re-authentication has failed, requiring multiple
reloads. It seems that once the re-direct succeeds, Camino "remembers" it until
the program is quit.

During the reload attempts, the status bar shows the destination URL. When the
"no data" dialog appears, the status bar shows the BMgr URL. On successful
attempts, the status bar shows the BMgr URL initially, then the authentication
screen appears.

I know my version is not the latest nightly... I will download a more recent
version and test it tomorrow.

Netscape and Mozilla do not exhibit this problem. Hope this helps.

--> John
(Reporter)

Comment 3

15 years ago
I've had the opportunity this morning to test the 5/17 nightly (2003051705). I
was unable to access the authentication page at all, even after more than 25
re-load attempts. During the connection attempts, the status bar initially shows
"Connect to www.google.com" for several seconds. Then, the status bar changes to
"Connect to 10.1.1.14" (the proxy server IP address), and almost immediately
after, the "Document contains no data" dialog appears.

During a successful connection (using the .7 beta), the sequence goes "Connect
to www.google.com", followed by "Transferring data from 10.1.1.14", then the
authentication screen appears.

It almost seems that the re-direct issued by Bordermanager causes a timeout
rather than a re-direct within Camino. Of course, this is purely speculation as
I am not a coder. Hope this helps.

--> John
(Assignee)

Comment 4

15 years ago
not sure how to test.
Assignee: saari → pinkerton
Target Milestone: --- → Camino1.1
John could you trace the the htp session using the instructions found at :
http://www.mozilla.org/projects/netlib/http/http-debugging.html and attache the
generated logs to this bug please.

Comment 6

14 years ago
Reporter please update, this bug is on m list of bugs to close as no one has
updated in almost a year now.

Comment 7

13 years ago
Closing for the above reason.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.