175045 - web page load return 'done' status with a blank screen

Status: VERIFIED DUPLICATE of bug 172791

(Core Graveyard :: Security: UI, defect)

Description

[Andy Wozniak]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.2a/mozilla-win32-1.2a-installer.exe

We are running IBM's QuickPlace server for corporate use.  Attempts to connect
to the server (sorry, no external access) with Mozilla 1.2a produces a blank
screen, the status says 'done'.

IBM's web site for their QUickPlace product menstions that NS 4.7x is only
supported and that a bug has been logged (since 2001) to remedy this.  Don't
know if our current version of QuickPlace has the fix.  Their QuickPlace
knowledge base noted some type of issue with IFRAMES. 

Just noticed that 1.1b is out, will try that version and will follow up on the
bug report.


Reproducible: Always

Steps to Reproduce:
1. URL https://qp.mc.com
2. go


Actual Results:  
'done' status
blank screen

Expected Results:  
display the home page for our QuickPlace server.

This problem is NOT observed when running Mozilla 1.1

Comment 1

[Matthias Versen [:Matti]]

Reporter:
Can you disable TLS in edit\prefernces\Privacy..\SSL and try again ?

Comment 2

[Andy Wozniak]

Just tried 1.1b and the problem persists.

BTW, forget about the blank screen, here's an updated seen of events:

1. URL https://qp.mc.com 
2. go
3. popup: The connection tp qp.mc.com has terminate unexpectedly. Some data may
have been transferred.
4. browser window remains at current web page - doesn't go blank as claimed.

Comment 3

[Andy Wozniak]

I disabled TLS per your suggestion and now the webpage opens properly.

I'll have to investigate what TLS is and whether our IS folks should be made
aware of this.

Thanks, you are a god.

Comment 4

[Matthias Versen [:Matti]]

TLs is the new ssl version (but already old).
Your server should be upgraded to support TLS.

Mozilla can detect TLS intolerant servers but this is broken in your build.
(that's why m1.1 works)

The fix is already in the tree (a few hours after we released 1.2b) and 1.2final
should be working.

*** This bug has been marked as a duplicate of 172791 ***

Comment 5

[John Unruh]

Verified dupe.