New issue
Advanced search Search tips

Issue 602415 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task

Blocking:
issue 599523



Sign in to add a comment

Fuzz HttpNetworkTransaction

Project Member Reported by mmenke@chromium.org, Apr 11 2016

Issue description

We should fuzz HttpNetworkTransaction, with a mock HttpStream.  We can fuzz the headers, number/length of reads, and maybe the final error message.  In some cases, HttpNetworkTransaction can retry requests - we could get data from them from the fuzzer input as well, or just have retries fail.
 

Comment 1 by mmenke@chromium.org, Apr 11 2016

Also, should be careful of HTTP 100 responses, where headers are read twice!

Comment 2 by mmenke@chromium.org, Apr 14 2016

It may actually be easier to mock things out at the socket layer, though it would result in a less focused test.
Owner: maksim.s...@intel.com
Status: Assigned (was: Available)
I'll take a look into it.
Owner: maksim.sisov@chromium.org
Owner: ----
Status: Available (was: Assigned)
Project Member

Comment 6 by sheriffbot@chromium.org, May 1 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Type-Bug Type-Task
Status: Available (was: Untriaged)

Comment 8 by mmenke@chromium.org, May 23 2018

Labels: Network-Triaged
Components: Internals>Network
Components: -Internals>Network>HTTP

Sign in to add a comment