clean up TLS intolerant "restart" code

RESOLVED FIXED in psm2.4

Status

Core Graveyard
Security: UI
RESOLVED FIXED
15 years ago
a year ago

People

(Reporter: Darin Fisher, Assigned: Darin Fisher)

Tracking

Other Branch
psm2.4

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

1.68 KB, patch
kaie
: review+
Brian Ryner (not reading)
: superreview+
Details | Diff | Splinter Review
(Assignee)

Description

15 years ago
If a site is found to be TLS intolerant, nsNSSIOLayer will signal necko to
restart the connection.  If detected on PR_Read, nsNSSIOLayer returns 0;
however, if detected on PR_Write, nsNSSIOLayer returns -1 with
PR_CONNECT_RESET_ERROR.  it should really set PR_CONNECT_RESET_ERROR in both cases.
(Assignee)

Comment 1

15 years ago
Created attachment 113177 [details] [diff] [review]
v1 patch
(Assignee)

Updated

15 years ago
Attachment #113177 - Flags: review?(kaie)
(Assignee)

Updated

15 years ago
Attachment #113177 - Flags: superreview?(bryner)

Comment 2

15 years ago
Comment on attachment 113177 [details] [diff] [review]
v1 patch

r=kaie
Attachment #113177 - Flags: review?(kaie) → review+
Attachment #113177 - Flags: superreview?(bryner) → superreview+

Updated

14 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → 2.4

Comment 3

14 years ago
Fix checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
(Assignee)

Comment 4

14 years ago
thank you jgmyers!  i completely forgot about this patch.  my normal bug queries
only cover mozilla milestones :-/

Updated

13 years ago
Component: Security: UI → Security: UI
Product: PSM → Core
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.