Closed
Bug 1277488
Opened 8 years ago
Closed 8 years ago
Make ProtocolParser pver-aware
Categories
(Toolkit :: Safe Browsing, defect)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
INVALID
People
(Reporter: hchang, Assigned: hchang)
References
Details
Attachments
(1 file, 1 obsolete file)
12.75 KB,
patch
|
Details | Diff | Splinter Review |
ProtocolParser definitely behaves differently for different protocol version. We need to make it protocol-version aware. This bug is not to implement v4 protocol parsing but provide a stub function to work with Bug 1276595
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → hchang
Assignee | ||
Comment 1•8 years ago
|
||
Assignee | ||
Updated•8 years ago
|
Blocks: safebrowsingv4
Assignee | ||
Comment 2•8 years ago
|
||
Attachment #8759118 -
Attachment is obsolete: true
Comment 3•8 years ago
|
||
The component is self-explained. Not necessary to identify SafeBrowsing in the title.
Summary: [Safe Browsing] Make ProtocolParser pver-aware → Make ProtocolParser pver-aware
Updated•8 years ago
|
Assignee | ||
Comment 4•8 years ago
|
||
I'd like to close this bug first since we changed the design so that we could use the table name to decide how we process the incoming data.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•