[WebSocket] Pass received status code of 0 to script as-is

[WebSocket] Pass received status code of 0 to script as-is

0 is not a valid close code, but we're passing through the other invalid
codes. Let's apply the rule also to 0 for consistency.

R=ricea
BUG=428794
Committed: https://crrev.com/ceae3b2476b441367dd75ede1c7781c1094c8ffa
Cr-Commit-Position: refs/heads/master@{#302233}

[tyoshino (SeeGerritForStatus), 2014-10-30 15:47:33]

tyoshino@chromium.org changed reviewers:
+ ricea@chromium.org

[tyoshino (SeeGerritForStatus), 2014-10-31 03:18:27]

Keeping 0 rejected is another choice. I'd like to hear your opinion, Adam-san.

[Adam Rice, 2014-10-31 03:58:10]

LGTM

The current behaviour is accidental, let's fix it first of all.

I think codes 0 to 999 are strongly invalid by RFC6455 and it is desirable to
discourage people from using them. However, it's low priority.

[tyoshino (SeeGerritForStatus), 2014-10-31 05:59:23]

The CQ bit was checked by tyoshino@chromium.org

[commit-bot: I haz the power, 2014-10-31 05:59:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/690753009/20001

[commit-bot: I haz the power, 2014-10-31 06:43:26]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-10-31 06:44:02]

Patchset 2 (id:??) landed as
https://crrev.com/ceae3b2476b441367dd75ede1c7781c1094c8ffa
Cr-Commit-Position: refs/heads/master@{#302233}