1. Who is/are the point of contact(s) for this review? 2. Please provide a short description of the feature / application (e.g. problem solved, use cases, etc.): 3. Please provide links to additional information (e.g. feature page, wiki) if available and not yet included in feature description: 4. Does this request block another bug? If so, please indicate the bug number 5. This review will be scheduled amongst other requested reviews. What is the urgency or needed completion date of this review? 6. Please answer the following few questions: (Note: If you are asked to describe anything, 1-2 sentences shall suffice.) 6a. Does this feature or code change affect Firefox, Thunderbird or any product or service the Mozilla ships to end users? 6b. Are there any portions of the project that interact with 3rd party services? 6c. Will your application/service collect user data? If so, please describe 7. If you feel something is missing here or you would like to provide other kind of feedback, feel free to do so here (no limits on size): 8. Desired Date of review (if known from https://firstname.lastname@example.org/Security%20Review.html) and whom to invite.
we already did a pipeline secreview https://wiki.mozilla.org/Security/Reviews/Firefox9/ReviewNotes/HTTPPipelines
getting around to sweeping bugs in our area and I see this is still around. I know we did a review in the past....is the bug this is blocking fundamentally the same code? Is this the situation where we just need to possible discuss it being on by default? Or is this a full skip?
there is nothing new to discuss here and I don't know why this bug was filed.
(In reply to Patrick McManus [:mcmanus] from comment #3) > there is nothing new to discuss here and I don't know why this bug was filed. sounds like things got disconnected at some point, I will kill this off then.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.