Closed
Bug 1422688
Opened 8 years ago
Closed 8 years ago
Blocking reads aren't compatible with 0-RTT
Categories
(NSS :: Libraries, enhancement)
NSS
Libraries
Tracking
(Not tracked)
RESOLVED
FIXED
3.35
People
(Reporter: mt, Assigned: mt)
Details
Attachments
(1 obsolete file)
The code added for Bug 1386475 to ensure correct ordering of early data relied on returning PR_WOULD_BLOCK from certain functions. In blocking mode (a mode that selfserv uses), this is returned, which the user of the blocking mode socket doesn't expect.
Updated•8 years ago
|
Attachment #8934092 -
Attachment is obsolete: true
| Assignee | ||
Updated•8 years ago
|
Attachment #8934092 -
Attachment is obsolete: false
| Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.35
Comment 1•8 years ago
|
||
Comment on attachment 8934092 [details]
Bug xxxxx - Fix for blocking mode reads of 0-RTT, r?ekr
Eric Rescorla (:ekr) has approved the revision.
https://phabricator.services.mozilla.com/D296
Attachment #8934092 -
Attachment is obsolete: true
Attachment #8934092 -
Flags: review+
You need to log in
before you can comment on or make changes to this bug.
Description
•