Revert of service worker: use 200 OK for update requests even in the no update case

Revert of service worker: use 200 OK for update requests even in the no update case (patchset #8 id:140001 of https://codereview.chromium.org/1675613002/ )

Reason for revert:
https://build.chromium.org/p/chromium.memory/builders/Linux%20ASan%20LSan%20Tests%20%281%29?numbuilds=200 got much more flaky after this landed. Speculatively revert and see if it helps. See also http://crbug.com/586897

Original issue's description:
> service worker: use 200 OK for update requests even in the no update case
>
> The main motivation is to stop network failure error spew in DevTools console.
> This patch reinstates the "pause on download" functionality we once had.
>
> BUG=541797
>
> Committed: https://crrev.com/42bc9253c79fa01fc6a6af5b3908dcc063a12023
> Cr-Commit-Position: refs/heads/master@{#376032}

TBR=tkent@chromium.org,michaeln@chromium.org,nhiroki@chromium.org,tsepez@chromium.org,falken@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=541797
Committed: https://crrev.com/5e2979f2431af7f900242b0a8c9e02c4f7dfe1db
Cr-Commit-Position: refs/heads/master@{#376161}

[Nico, 2016-02-18 13:47:01]

Created Revert of service worker: use 200 OK for update requests even in the no
update case

[commit-bot: I haz the power, 2016-02-18 13:47:19]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1710903002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1710903002/1

[commit-bot: I haz the power, 2016-02-18 13:48:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-18 13:49:26]

Description was changed from

==========
Revert of service worker: use 200 OK for update requests even in the no update
case (patchset #8 id:140001 of https://codereview.chromium.org/1675613002/ )

Reason for revert:
https://build.chromium.org/p/chromium.memory/builders/Linux%20ASan%20LSan%20T...
got much more flaky after this landed. Speculatively revert and see if it helps.
See also http://crbug.com/586897

Original issue's description:
> service worker: use 200 OK for update requests even in the no update case
> 
> The main motivation is to stop network failure error spew in DevTools console.
> This patch reinstates the "pause on download" functionality we once had.
> 
> BUG=541797
> 
> Committed: https://crrev.com/42bc9253c79fa01fc6a6af5b3908dcc063a12023
> Cr-Commit-Position: refs/heads/master@{#376032}

TBR=tkent@chromium.org,michaeln@chromium.org,nhiroki@chromium.org,tsepez@chro...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=541797
==========

to

==========
Revert of service worker: use 200 OK for update requests even in the no update
case (patchset #8 id:140001 of https://codereview.chromium.org/1675613002/ )

Reason for revert:
https://build.chromium.org/p/chromium.memory/builders/Linux%20ASan%20LSan%20T...
got much more flaky after this landed. Speculatively revert and see if it helps.
See also http://crbug.com/586897

Original issue's description:
> service worker: use 200 OK for update requests even in the no update case
>
> The main motivation is to stop network failure error spew in DevTools console.
> This patch reinstates the "pause on download" functionality we once had.
>
> BUG=541797
>
> Committed: https://crrev.com/42bc9253c79fa01fc6a6af5b3908dcc063a12023
> Cr-Commit-Position: refs/heads/master@{#376032}

TBR=tkent@chromium.org,michaeln@chromium.org,nhiroki@chromium.org,tsepez@chro...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=541797

Committed: https://crrev.com/5e2979f2431af7f900242b0a8c9e02c4f7dfe1db
Cr-Commit-Position: refs/heads/master@{#376161}
==========

[commit-bot: I haz the power, 2016-02-18 13:49:27]

Patchset 1 (id:??) landed as
https://crrev.com/5e2979f2431af7f900242b0a8c9e02c4f7dfe1db
Cr-Commit-Position: refs/heads/master@{#376161}

[Nico, 2016-02-18 19:30:56]

looks like this helped, bot had 6 consecutive green runs after this went in,
preceded by 11 out of 12 failing before the revert