tree cd600f726f7f1ae1fc51328956d0e76129692512
parent 982f5106ac110deaec8b5789a4ac8035a268f4ce
author Brian Norris <briannorris@chromium.org> 1474998219 -0700
committer Mike Frysinger <vapier@chromium.org> 1531794978 +0000

cros_sdk: fix more quirks and corner cases in parsing curl HTTP responses

See section 3.1 here:

https://www.ietf.org/rfc/rfc2616.txt

that says:

"""
   The version of an HTTP message is indicated by an HTTP-Version field
   in the first line of the message.

       HTTP-Version   = "HTTP" "/" 1*DIGIT "." 1*DIGIT
"""

However, we've seen reports in the wild of (potentially non-conforming?)
HTTP/2 implementations returning 'HTTP/2 200 OK'. Rather than being
unnecessarily pedantic here, let's just accept the not-so-standard
format.

While we're at it, I noticed that the HTTP standard allows for these
major/minor revisions to roll over to 2+ digits.

And finally, note that '.' is a regex wildcard. Let's escape it
properly.

So, a few representative examples of prefixes we accept:

  'HTTP/1.0 200'
  'HTTP/1.1 200'
  'HTTP/1 200'
  'HTTP/2.0 200'
  'HTTP/2 200'
  'HTTP/99999 200'
  'HTTP/1337.987654321 200'

But we no longer allow:

  'HTTP/1a0 200'

BUG=chromium:541462
TEST=trybots; download a new checkout / build the cros_sdk chroot

Change-Id: I804a0bd13f50ddaec1f6a6b7fe0fd16f5aa9167d
(cherry picked from commit cf8aef44686e40e4899a332587ca0ca0b8c58a51)
Reviewed-on: https://chromium-review.googlesource.com/1139636
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>