Closed Bug 88142 Opened 23 years ago Closed 23 years ago

TLS through proxy needs to work.

Categories

(Core Graveyard :: Security: UI, defect, P1)

1.0 Branch
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 88244
psm2.1

People

(Reporter: javi, Assigned: javi)

Details

For the next version of PSM, we need to make sure that a user can enable TLS and set up a proxy at the same time. With the current version of PSM, we're seeing it is hard to provide the TLS->SSL v3.0 retry so we need to solve this problem so it can be used.
target -> 2.1 P2 Commercial customers commonly use a proxy: keyword nsenterprise.
Keywords: nsenterprise
Priority: -- → P1
Target Milestone: --- → 2.1
->javi
Assignee: ssaux → javi
Currently the fix to bug 87902 is to detect that a proxy is used and turn off TLS, regardless of whether the site is TLS intolerant. Fix to bug 64888 is to attempt TLS, and only go to SSL 3.0 if TLS fails. According to bug 88244, we should know be able to have the same behavior from bug 64888 when dealing with proxies.
dup of 88244 which has all the necko folks cc'ed *** This bug has been marked as a duplicate of 88244 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Verified dupe.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.