If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[RFE]Make these pages work in SSL mode even when TLS is enabled (default) in PSM.

VERIFIED FIXED

Status

Tech Evangelism Graveyard
English US
P2
enhancement
VERIFIED FIXED
17 years ago
3 years ago

People

(Reporter: hirata masakazu, Assigned: Katsuhiko Momoi)

Tracking

Details

(Whiteboard: [BANKING][TLS], URL)

(Reporter)

Description

17 years ago
2001011104.
I can not load the URL. Throbber stops quickly after "Sending request to ...".
Cookies are Accept All, and no site is blocked under the Preferences. I have no
idea whats going on. Other SSL sites work fine AFAIK.

Comment 1

17 years ago
This site seems not to be TLS aware. Please open the PSM (padlock icon at the
bottom right corner), go to "Advanced ... Options", deselect "TLS" and try again.
Does it work now? (It works for me on NT4.)
(Reporter)

Comment 2

17 years ago
Thank you.  It worked for me, too.
 What should I do with this bug entry?
Should it be marked invalid, or is it still a bug if enabling TLS in PSM blocks
something from working?
Summary: Can not load a page in SSL mode. → Can not load a page in SSL mode when TLS is enabled (default) in PSM.

Comment 3

17 years ago
Over to Evangelism ... I think that's where this kind of bug belongs to.
Assignee: ddrinan → evangelism
Component: Security: Crypto → Evangelism
OS: Mac System 9.x → All
QA Contact: junruh → zach
Hardware: Macintosh → All
(Reporter)

Comment 4

17 years ago
Here is another URL that can not be reached until TLS is disabled from PSM:
https://e-banking.abbeynational.co.uk
Changing the summary, component, and setting Severity to Critical, since I can foresee support 
issues in the final release if this is not somehow fixed.
Please feel free to change the summary or component appropriately.
Severity: normal → critical
Component: Evangelism → Security: Crypto
Summary: Can not load a page in SSL mode when TLS is enabled (default) in PSM. → Make these pages work in SSL mode even when TLS is enabled (default) in PSM.
(Reporter)

Updated

17 years ago
Summary: Make these pages work in SSL mode even when TLS is enabled (default) in PSM. → [RFE]Make these pages work in SSL mode even when TLS is enabled (default) in PSM.

Comment 5

17 years ago
see bug 59321

Comment 6

17 years ago
Over to evangelism.
Assignee: evangelism → blakeross
Component: Security: Crypto → Evangelism

Comment 7

17 years ago
Reassigning evangelism bugs to new owner (bclary@netscape.com).
Assignee: blakeross → bclary

Updated

17 years ago
Whiteboard: [BANKING][TLS]

Comment 8

17 years ago
kat, giving this one to you if you don't mind.
Assignee: bclary → momoi
(Assignee)

Comment 9

17 years ago
This site uses:

Domino-Go-Webserver/4.6.2.8

which is a known server with TLS/SSL3.0 rollback
problem. 
The problem has been fixed in recent builds (6/18 or 
thereabouts) in that there is now built-in graceful 
rollack even when Mozilla encounters an incorrectly 
implemented SSL server like this one.
We should still send JAL a note reminding them to
upgrade their server.

Setting priority to P2.
Status: NEW → ASSIGNED
Priority: -- → P2
(Assignee)

Comment 10

17 years ago
See this bug report for details of TLS/SSL rollback
problem:

http://bugzilla.mozilla.org/show_bug.cgi?id=59321

Comment 11

16 years ago
Marking fixed. Try the sites with a newer build.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 12

16 years ago
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified

Comment 13

16 years ago
page opens fine -> verified
Status: RESOLVED → VERIFIED

Updated

16 years ago
Keywords: evang500

Comment 14

15 years ago
[RFE] is deprecated in favor of severity: enhancement.  They have the same meaning.
Severity: critical → enhancement
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.