Script fails to allow responses with HTTP/2 200

[matthewdarwin]

HTTP/2 200 should be considered a valid HTTP response for this script. The script is only checking 200 OK

curl -H "Origin: https://scattellet.com" "https://api.eosn.io/v1/chain/get_info" --verbose --max-time 1 --stderr -                    
*   Trying 174.138.114.204...
* TCP_NODELAY set
* Connected to api.eosn.io (174.138.114.204) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=eosn.io
*  start date: Jun  3 18:02:42 2018 GMT
*  expire date: Sep  1 18:02:42 2018 GMT
*  subjectAltName: host "api.eosn.io" matched cert's "api.eosn.io"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x5591d46bf8e0)
> GET /v1/chain/get_info HTTP/2
> Host: api.eosn.io
> User-Agent: curl/7.58.0
> Accept: */*
> Origin: https://scattellet.com
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200
< access-control-allow-origin: *
< content-length: 554
< content-type: application/json
< server: WebSocket++/0.7.0
< date: Sat, 23 Jun 2018 16:12:59 GMT
<
[response omitted]