nsHttpResponseHead: Some functions can be made private...
Categories
(Core :: Networking: HTTP, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox95 | --- | fixed |
People
(Reporter: alfredkayser, Assigned: sd2187)
Details
(Keywords: good-first-bug, Whiteboard: [necko-would-take])
Attachments
(1 file)
Comment 1•20 years ago
|
||
Reporter | ||
Comment 2•20 years ago
|
||
Updated•19 years ago
|
Reporter | ||
Comment 3•18 years ago
|
||
Updated•9 years ago
|
Comment 4•9 years ago
|
||
Updated•9 years ago
|
Comment 5•7 years ago
|
||
Updated•5 years ago
|
Comment 6•4 years ago
|
||
This good-first-bug hasn't had any activity for 6 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.
Hello,
I am Somdatta and I am an outreachy applicant.I wanted to know whether this bug has been resolved or not.If not,I would like to work on it.
Thanks
Comment 8•3 years ago
•
|
||
While some of the functions changed slightly, the general intent seems still valuable here, IMHO. Dragana, wdyt?
Updated•3 years ago
|
Assignee | ||
Comment 10•3 years ago
|
||
Okay.I am working on it then.
One question,who should I submit a patch for review to?
Comment 11•3 years ago
|
||
Please follow this guide on how to submit a patch with moz-phab
. As reviewer you can put r?#necko-reviewers
into the commit message. Thanks!
Assignee | ||
Comment 12•3 years ago
|
||
okay
Assignee | ||
Comment 13•3 years ago
|
||
Make the following functions private because they are only used in nsHttpResponseHead.cpp for compiler optimization-
GetDateValue,GetAgeValue,GetMaxAgeValue,GetExpiresValue.
GetLastModifiedValue cannot be made private since it is being used in CachePushChecker.cpp and ParseDateHeader is already private.
Updated•3 years ago
|
Comment 14•3 years ago
|
||
Assignee | ||
Comment 15•3 years ago
|
||
Just wanted to confirm..the submitted patch has been landed right?
Comment 16•3 years ago
•
|
||
(In reply to Somdatta from comment #15)
Just wanted to confirm..the submitted patch has been landed right?
It is not yet in central. Now automated tests and other behind the scenes verification is running. You will see a second message here once it is there.
Assignee | ||
Comment 17•3 years ago
|
||
okay
Comment 18•3 years ago
|
||
bugherder |
Description
•