Closed Bug 98908 Opened 23 years ago Closed 23 years ago

HTTPS (SSL) pages are broken

Categories

(Core :: Networking, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 97606

People

(Reporter: Morten, Assigned: darin.moz)

References

()

Details

Attachments

(3 files)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.3+)
Gecko/20010908
BuildID:    2001090808

Pages using SSL are not working as the should. another HTTPS site (account is
needed to show it) isn't loaded by mozilla when the browser has focus.


Reproducible: Always
Steps to Reproduce:
1. open nettbank.sparebank1.no
2. get redirected to login page

Actual Results:  Blank page was shown

Expected Results:  login page should be shown
The bug with browser focus mentioned is also present for non-ssl pages, filed
bug 98911 on it
I just took a wild guess and typed in 22223441123 as Kontonummer (=account
number) and it took me to the login page then.

I'll attach a screenshot below of what I refer to as the login page to make sure
it's the same one as Morten can't reach.

WORKSFORME with 2001-09-07-21 on Linux.
Could someone using Windows 2000 try this?
it seems to me that this is a win32 specific bug.

on my computer I was never asked to enter an account number.
I have confirmed the behavior mentioned in the bug using build 2001091003 under
Windows 2000sp2.  I get a blank page shown, nothing in the page source.  To be
sure it wasn't a server problem, I tried going in with Opera identifying itself
as Netscape 5 and received the login page correctly.  I'd suggest making this a
confirmed bug (my bugzilla login doesn't allow me to do this).
-> new.
let me know if you need anything else done to this bug!
Status: UNCONFIRMED → NEW
Ever confirmed: true
https://login.yahoo.com does not load at all with Mozilla 0.9.4 (RH7x build).
I've reinstalled Mozilla (Navigator only + SSL) from scratch and also got rid of
existing config files and all of a sudden it works for me. So, please kindly
ignore previous comment.
>Could someone using Windows 2000 try this?
>it seems to me that this is a win32 specific bug.


I am also seeing this on Windows2000 using Mozilla 0.9.4.  I'll try to generate
some screenshots and submit them.

However, not all https sites are presenting problems.  My https webmail system
is working fine - I can get into my account status (https) at amazon.com - I can
login using ssl on Sourceforge.  However, several other https sites (for
example, our web portal at work) is not working.

I haven't tried this on Linux yet to verify that it works on Linux - I'll try it
at home tonight on RH71 and report back.

-jh
darin
Assignee: neeti → darin
I see a pattern here.  Maybe this will mean something to someone.

All of our https web apps that use Sun's Java Web Server 2.0 / Solaris return
with "Not Acceptable (406)" using Mozilla 0.9.4 / Win2000.  I don't even see
anything in the access_log to indicate a GET request was serviced by JWS.

Our https web apps that runs on Apache 1.3.6 / Linux do not return any page
content, and nothing in Show Source.

Interestingly, one of the Apache  https web apps is protected behind htpasswd. 
I _am_ prompted for a username/password here, and only after I authenticate do I
get an empty page with nothing in Show Source.

-jh
Have verified that the same behavior occurs using Mozilla 0.9.4 / WinNT4(SP6):

- Our https web apps that runs on Apache 1.3.6 / Linux do not return any page
content, and nothing in Show Source.

- Interestingly, one of the Apache  https web apps is protected behind htpasswd. 
I _am_ prompted for a username/password here, and only after I authenticate do I
get an empty page with nothing in Show Source.


-jh
I have found a work-around for this bug.  Mozilla 0.9.4 does not ship with a
default character encoding set up in the preferences.  If I manually go into:

Edit - Preferences - Navigator - Languages

And from here, under 'Character coding / Default character coding', I can set
the default character coding.  There wasn't one set by default.  If I set this
value to *anything*, I can get into *all* of the https apps.

Yes, I think you really can set the character coding to anything.  I first tried
ISO-8859-1, but also seems to work fine with a character coding that I don't
think my box currently has.


-jh
  Verified this workaround under NT4.0 (SP6).


*** This bug has been marked as a duplicate of 97606 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: