Closed
Bug 138001
Opened 24 years ago
Closed 24 years ago
HTTPS site not accessible through proxy
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 102098
People
(Reporter: khollenshead, Assigned: Matti)
References
()
Details
Attachments
(1 file)
|
511 bytes,
text/plain
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1)
Gecko/20020416
BuildID: 2002041617
I recently tried to access some financial sites via Mozilla and was unable to
get to them. I get about:blank after a 10-15 seconds and the throbber stops.
There is no crash - just a blank page. I have been able to use Mozilla to view
them previously but I cannot pin down a timeframe when they were working. I do
know that they work when I am at home (Win98) and connect directly without using
a proxy. I am able to get to some sites but not others. I have included some
that work and some that don't so that perhaps differences in the sites can be noted.
NOT Working:
https://www.cafcu.org/onlineserv/HB/signon.cgi?signon.html
https://investing.schwab.com/trading/start
Working:
https://netbenefits.401k.com/NBLogin/
I am behind a firewall that is configured via an auto-proxy configuration. NS
4.79 works fine with the same auto-proxy config script and I am able to access
all of the sites fine. I reinstalled the Mozilla build cleanly, deleting all
files and creating a new profile. I also turned off TLS and reverted to HTTP
1.0 and tried, to no avail.
The HTTPS proxy gets configured on port 80 from the auto-configuration script.
Reproducible: Always
Steps to Reproduce:
1. Setup auto-proxy configuration
2. Browse to one of the sites listed.
Actual Results: Received about:blank page.
Expected Results: Page to be displayed.
| Reporter | ||
Comment 1•24 years ago
|
||
This is the proxy auto-config file that I use (minus the internal IP ranges and
hostnames for my company).
dup of bug 102098 / bug 103311 ?
*** This bug has been marked as a duplicate of 102098 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Comment 5•24 years ago
|
||
Verified. The non-working sites mentioned are SSL2 only.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•