Revert of HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes.

Revert of HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes. (patchset #4 id:60001 of https://codereview.chromium.org/2170133004/ )

Reason for revert:
Speculative revert for bug 631246.  Have no better ideas.

Apologies if this wasn't the cause.

Original issue's description:
> HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes.
>
> We were using HexStringToInt to parse chunk size, which returns a
> 32-bit int.  This CL switches to using HexStringToInt64, which uses
> 64-bit ints, so we can now support chunks up to 2^63-1 bytes.
>
> That should be enough for anybody. [Cue dramatic music]
>
> BUG=630680
>
> Committed: https://crrev.com/8ea249f8b70f154f9995ed538fc853fe9cf46503
> Cr-Commit-Position: refs/heads/master@{#407549}

TBR=eroman@chromium.org,mmenke@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=630680
Committed: https://crrev.com/2321e8a45603ca595296b67e4d064c070f2b3591
Cr-Commit-Position: refs/heads/master@{#407651}

[Mark P, 2016-07-26 00:31:19]

The CQ bit was checked by mpearson@chromium.org

[Mark P, 2016-07-26 00:31:20]

Created Revert of HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes.

[commit-bot: I haz the power, 2016-07-26 00:32:36]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-26 00:33:43]

Description was changed from

==========
Revert of HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes. (patchset
#4 id:60001 of https://codereview.chromium.org/2170133004/ )

Reason for revert:
Speculative revert for bug 631246.  Have no better ideas.

Apologies if this wasn't the cause.


Original issue's description:
> HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes.
> 
> We were using HexStringToInt to parse chunk size, which returns a
> 32-bit int.  This CL switches to using HexStringToInt64, which uses
> 64-bit ints, so we can now support chunks up to 2^63-1 bytes.
> 
> That should be enough for anybody. [Cue dramatic music]
> 
> BUG=630680
> 
> Committed: https://crrev.com/8ea249f8b70f154f9995ed538fc853fe9cf46503
> Cr-Commit-Position: refs/heads/master@{#407549}

TBR=eroman@chromium.org,mmenke@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=630680
==========

to

==========
Revert of HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes. (patchset
#4 id:60001 of https://codereview.chromium.org/2170133004/ )

Reason for revert:
Speculative revert for bug 631246.  Have no better ideas.

Apologies if this wasn't the cause.


Original issue's description:
> HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes.
> 
> We were using HexStringToInt to parse chunk size, which returns a
> 32-bit int.  This CL switches to using HexStringToInt64, which uses
> 64-bit ints, so we can now support chunks up to 2^63-1 bytes.
> 
> That should be enough for anybody. [Cue dramatic music]
> 
> BUG=630680
> 
> Committed: https://crrev.com/8ea249f8b70f154f9995ed538fc853fe9cf46503
> Cr-Commit-Position: refs/heads/master@{#407549}

TBR=eroman@chromium.org,mmenke@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=630680
==========

[commit-bot: I haz the power, 2016-07-26 00:33:44]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-26 00:34:59]

Description was changed from

==========
Revert of HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes. (patchset
#4 id:60001 of https://codereview.chromium.org/2170133004/ )

Reason for revert:
Speculative revert for bug 631246.  Have no better ideas.

Apologies if this wasn't the cause.


Original issue's description:
> HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes.
> 
> We were using HexStringToInt to parse chunk size, which returns a
> 32-bit int.  This CL switches to using HexStringToInt64, which uses
> 64-bit ints, so we can now support chunks up to 2^63-1 bytes.
> 
> That should be enough for anybody. [Cue dramatic music]
> 
> BUG=630680
> 
> Committed: https://crrev.com/8ea249f8b70f154f9995ed538fc853fe9cf46503
> Cr-Commit-Position: refs/heads/master@{#407549}

TBR=eroman@chromium.org,mmenke@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=630680
==========

to

==========
Revert of HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes. (patchset
#4 id:60001 of https://codereview.chromium.org/2170133004/ )

Reason for revert:
Speculative revert for bug 631246.  Have no better ideas.

Apologies if this wasn't the cause.

Original issue's description:
> HttpChunkedDecoder: Support chunks longer than 2^31-1 bytes.
>
> We were using HexStringToInt to parse chunk size, which returns a
> 32-bit int.  This CL switches to using HexStringToInt64, which uses
> 64-bit ints, so we can now support chunks up to 2^63-1 bytes.
>
> That should be enough for anybody. [Cue dramatic music]
>
> BUG=630680
>
> Committed: https://crrev.com/8ea249f8b70f154f9995ed538fc853fe9cf46503
> Cr-Commit-Position: refs/heads/master@{#407549}

TBR=eroman@chromium.org,mmenke@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=630680

Committed: https://crrev.com/2321e8a45603ca595296b67e4d064c070f2b3591
Cr-Commit-Position: refs/heads/master@{#407651}
==========

[commit-bot: I haz the power, 2016-07-26 00:35:00]

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

[mmenke, 2016-07-26 04:00:51]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2180063002/ by mmenke@chromium.org.

The reason for reverting is: The CL was blamed for compile failures it didn't
cause, re-landing..