Add hyper as a Command Line Interface #82

t2y · 2015-01-31T15:21:38Z

I made the hyper command to run hyper quickly.

To use cli, install again hyper.

$ python setup.py develop

For example, it's easy to run for simple debugging.

$ hyper -v google.com
Selected NPN: h2-14
Sending frame SettingsFrame on stream 0
Received frame SettingsFrame on stream 0
Sending frame SettingsFrame on stream 0
Received frame WindowUpdateFrame on stream 0
HPACK encoding [(':method', 'GET'), (':scheme', 'https'), (':authority', 'google.com'), (':path', '/')]
...

Other options are here. They're encoding or do not show response data, and so on.

$ hyper -h
usage: hyper [-h] [-e ENCODING] [-n] [-m METHOD] [-v] host [path]

positional arguments:
  host                  set host to request
  path                  set path to resource (default: /)

optional arguments:
  -h, --help            show this help message and exit
  -e ENCODING, --encoding ENCODING
                        set charset for content-type
  -n, --nullout         do not show response data
  -m METHOD, --method METHOD
                        set http method (default: GET)
  -v, --verbose         set verbose mode (loglevel=DEBUG)

I'll implement if you want additional function or typical use. I have no idea what kind of functions is useful.

sigmavirus24 · 2015-01-31T15:25:32Z

So I may be a bit out of my role as a user, but this seems best as a 3rd party package, something that is built with hyper but does not need to be included in hyper itself. I see this as being something like what httpie is in relation to requests. Perhaps you could even implement this in httpie. @jakubroztocil care to comment as to whether httpie would like this?

t2y · 2015-01-31T15:46:28Z

Thank you for information. I didn't know httpie tool. That's quite cool and its dependency is requests only. If @jakubroztocil is interested in integrating hyper as a http2 library. I'll investigate and do it.

Lukasa · 2015-02-01T12:17:31Z

Holy wow @t2y, this is fantastic! I was briefly working on a tool like this myself but never got around to finishing or committing it.

I think having httpie grab this function would be interesting, and I'm happy to work with @jakubroztocil to make that happen, but in the meantime I think this is a great value-add for hyper. It should make it much easier for people to give HTTP/2 a try and to report bugs with the library.

With that said, I think we should emulate the CLI of httpie. Not all of it, but the initial feature set should use the same arguments and flags as httpie. Basically, don't add any new features (in this pull request), but do change the argument parsing to match httpie.

t2y · 2015-02-01T12:55:53Z

Thank you for your advice.

With that said, I think we should emulate the CLI of httpie.

I see. I'll investigate httpie more and more.

Not all of it, but the initial feature set should use the same arguments and flags as httpie. Basically, don't add any new features (in this pull request), but do change the argument parsing to match httpie.

I agree with you. My original motivation is to be able to use hyper quickly and simply for new users.

jkbrzt · 2015-02-01T13:36:33Z

@t2y 👍 for emulating HTTPie's CLI for these reasons:

HTTPie has many users who'll be immediately familiar with the interface.
Conversely, It will be easy to switch to HTTPie once it adds HTTP/2 support.
The CLI is (hopefully) quite polished and user-friendly.

@Lukasa I see there is already a requests integration. That's great! I will start looking into adding support for Hyper/HTTP2 directly to HTTPie. Perhaps as a plugin until it's more stable.

Lukasa · 2015-02-01T13:38:07Z

@jakubroztocil Doing it as a plugin is definitely the way forward, because right now we can't do upgrade very well, so you'd have to specify HTTP/2 ahead of time. Let me know if you want some help with the work.

See: httpie/cli#298 python-hyper/hyper#82

jkbrzt · 2015-02-06T13:55:52Z

@Lukasa I've updated the HTTPie plugin API to support transport adapters and created httpie-http2 that uses hyper.

hyper is giving me this error on Python 3.4:

$ http --debug  https://www.twitter.com
HTTPie 1.0.0-dev
HTTPie data: /Users/jakub/.httpie
Requests 2.5.1
Pygments 2.0.2
Python 3.4.2 (default, Oct 17 2014, 12:53:14)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.51)] darwin

>>> requests.request({'allow_redirects': False,
 'auth': None,
 'cert': None,
 'data': OrderedDict(),
 'files': DataDict(),
 'headers': {'User-Agent': b'HTTPie/1.0.0-dev'},
 'method': 'get',
 'params': ParamsDict(),
 'proxies': {},
 'stream': True,
 'timeout': 30,
 'url': 'https://www.twitter.com',
 'verify': True})

Traceback (most recent call last):
  File "/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/runpy.py", line 170, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/Users/jakub/Code/httpie/httpie/httpie/__main__.py", line 10, in <module>
    sys.exit(main())
  File "/Users/jakub/Code/httpie/httpie/httpie/core.py", line 112, in main
    response = get_response(args, config_dir=env.config.directory)
  File "/Users/jakub/Code/httpie/httpie/httpie/client.py", line 36, in get_response
    response = requests_session.request(**kwargs)
  File "/Users/jakub/.virtualenvs/httpie-py34/lib/python3.4/site-packages/requests/sessions.py", line 461, in request
    resp = self.send(prep, **send_kwargs)
  File "/Users/jakub/.virtualenvs/httpie-py34/lib/python3.4/site-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "/Users/jakub/.virtualenvs/httpie-py34/lib/python3.4/site-packages/hyper/contrib.py", line 59, in send
    request.headers
  File "/Users/jakub/.virtualenvs/httpie-py34/lib/python3.4/site-packages/hyper/http20/connection.py", line 149, in request
    self.endheaders(message_body=body, final=True, stream_id=stream_id)
  File "/Users/jakub/.virtualenvs/httpie-py34/lib/python3.4/site-packages/hyper/http20/connection.py", line 297, in endheaders
    self.connect()
  File "/Users/jakub/.virtualenvs/httpie-py34/lib/python3.4/site-packages/hyper/http20/connection.py", line 204, in connect
    sock = wrap_socket(sock, self.host)
  File "/Users/jakub/.virtualenvs/httpie-py34/lib/python3.4/site-packages/hyper/http20/tls.py", line 43, in wrap_socket
    assert ssl_sock.selected_npn_protocol() == NPN_PROTOCOL
AssertionError

Any idea how to fix that? (ssl_sock.selected_npn_protocol() returns 'http/1.1' btw)

Python 2.7 gives me this error:

$ http --debug  https://twitter.com
HTTPie 1.0.0-dev
HTTPie data: /Users/jakub/.httpie
Requests 2.5.1
Pygments 2.0.2
Python 2.7.9 (default, Dec 15 2014, 10:01:34)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] darwin

>>> requests.request({'allow_redirects': False,
 'auth': None,
 'cert': None,
 'data': OrderedDict(),
 'files': DataDict(),
 'headers': {'User-Agent': 'HTTPie/1.0.0-dev'},
 'method': 'get',
 'params': ParamsDict(),
 'proxies': {},
 'stream': True,
 'timeout': 30,
 'url': u'https://twitter.com',
 'verify': True})

Traceback (most recent call last):
  File "/Users/jakub/.virtualenvs/httpie/bin/http", line 9, in <module>
    load_entry_point('httpie==1.0.0-dev', 'console_scripts', 'http')()
  File "/Users/jakub/Code/httpie/httpie/httpie/core.py", line 112, in main
    response = get_response(args, config_dir=env.config.directory)
  File "/Users/jakub/Code/httpie/httpie/httpie/client.py", line 36, in get_response
    response = requests_session.request(**kwargs)
  File "/Users/jakub/.virtualenvs/httpie/lib/python2.7/site-packages/requests/sessions.py", line 461, in request
    resp = self.send(prep, **send_kwargs)
  File "/Users/jakub/.virtualenvs/httpie/lib/python2.7/site-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "/Users/jakub/.virtualenvs/httpie/lib/python2.7/site-packages/hyper/contrib.py", line 59, in send
    request.headers
  File "/Users/jakub/.virtualenvs/httpie/lib/python2.7/site-packages/hyper/http20/connection.py", line 149, in request
    self.endheaders(message_body=body, final=True, stream_id=stream_id)
  File "/Users/jakub/.virtualenvs/httpie/lib/python2.7/site-packages/hyper/http20/connection.py", line 297, in endheaders
    self.connect()
  File "/Users/jakub/.virtualenvs/httpie/lib/python2.7/site-packages/hyper/http20/connection.py", line 204, in connect
    sock = wrap_socket(sock, self.host)
  File "/Users/jakub/.virtualenvs/httpie/lib/python2.7/site-packages/hyper/http20/tls.py", line 32, in wrap_socket
    _context = _init_context()
  File "/Users/jakub/.virtualenvs/httpie/lib/python2.7/site-packages/hyper/http20/tls.py", line 52, in _init_context
    context = ssl.SSLContext(ssl.PROTOCOL_TLSv1_2)
AttributeError: 'NoneType' object has no attribute 'SSLContext'

Also, is there a way to enable hyper logging from the plugin?

Lukasa · 2015-02-06T16:08:36Z

@jakubroztocil Yeah, that assertion error is not as clean as it should be. Essentially, we're not negotiating the correct HTTP/2 draft with Twitter. The released version of hyper only claims support for h2-14, despite the fact that h2-16 and h2-15 should be binary-compatible with h2-14. Twitter advertises h2-15, so we need to advertise support for it if necessary.

I can push a release that causes hyper to do that. That said, my code seems to be having some trouble talking to Twitter at the moment (error code PROTOCOL_ERROR), so let me dig into that a bit before I do so.

Currently hyper doesn't support Python 2.7 because PyOpenSSL is basically useless.

As for enabling hyper logging, hyper uses standard python logging, under the hyper namespace. Standard logging practices should be enough here.

Lukasa · 2015-02-06T16:13:38Z

Suspect Twitter doesn't like one of my SETTINGS values, because nghttp2 has no complaints.

Lukasa · 2015-02-06T16:21:49Z

Yup, definitely a settings issue. From the logs:

INFO:hyper.http20.connection:Sending frame SettingsFrame on stream 0
INFO:hyper.http20.connection:Received frame SettingsFrame on stream 0
INFO:hyper.http20.connection:Sending frame SettingsFrame on stream 0
INFO:hyper.http20.connection:Received frame GoAwayFrame on stream 0

Lukasa · 2015-02-06T16:24:45Z

So Twitter doesn't like us sending a value for ENABLE_PUSH. Weird. Setting other settings values seems to work just fine.

Lukasa · 2015-02-06T16:26:05Z

Note that it doesn't matter what value I send for ENABLE_PUSH, either 0 or 1, Twitter seems to barf on it.

Lukasa · 2015-02-06T16:27:13Z

Ok, so I'm going to push the branch that advertises h2-15 and h2-16 support as well as h2-14, but note that Twitter is still misbehaving. @jakubroztocil, try testing against nghttp2.org in the short term. I may push a patch that stops us sending an ENABLE_PUSH setting, but I'm not sure.

jkbrzt · 2015-02-06T16:28:52Z

Okay, thanks for the info. It means the plugin should be functional (to the same degree as hyper is), so you can now use it with HTTPie. // cc @t2y

@Lukasa I'm getting ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600) when testing it against nghttp2.org

Lukasa · 2015-02-06T16:38:14Z

Interesting, I'm not getting it locally unless I update to a newer .pem file. I take it you're providing an explicit certificate bundle? Try using the one bundled with hyper for testing purposes: it's old, but it does validate nghttp2.org.

@tatsuhiro-t: With a recent Mozilla certificate bundle we're getting cert verification errors on nghttp2.org. Any thoughts as to why that might be?

Lukasa · 2015-02-06T16:41:27Z

Confusingly, if I use the PEM file with openssl s_client it connects just fine.

jkbrzt · 2015-02-06T16:42:25Z

@Lukasa I'm using the defaults:

$ mkvirtualenv hyper-test -p `which python3`
Running virtualenv with interpreter /usr/local/bin/python3
Using base prefix '/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework/Versions/3.4'
[…]

(hyper-test)~ $ pip install hyper
Downloading/unpacking hyper
  Downloading hyper-0.1.0-py2.py3-none-any.whl (212kB): 212kB downloaded
Installing collected packages: hyper
Successfully installed hyper
Cleaning up...

(hyper-test)~ $ python
>>> from hyper import HTTP20Connection
>>> conn = HTTP20Connection('nghttp2.org:443')
>>> conn.request('GET', '/')
---------------------------------------------------------------------------
SSLError                                  Traceback (most recent call last)
<ipython-input-3-685be65690da> in <module>()
----> 1 conn.request('GET', '/')

/Users/jakub/.virtualenvs/hyper-test/lib/python3.4/site-packages/hyper/http20/connection.py in request(self, method, url, body, headers)
    147             body = body.encode('utf-8')
    148
--> 149         self.endheaders(message_body=body, final=True, stream_id=stream_id)
    150
    151         return stream_id

/Users/jakub/.virtualenvs/hyper-test/lib/python3.4/site-packages/hyper/http20/connection.py in endheaders(self, message_body, final, stream_id)
    295         :returns: Nothing.
    296         """
--> 297         self.connect()
    298
    299         stream = self._get_stream(stream_id)

/Users/jakub/.virtualenvs/hyper-test/lib/python3.4/site-packages/hyper/http20/connection.py in connect(self)
    202         if self._sock is None:
    203             sock = socket.create_connection((self.host, self.port), 5)
--> 204             sock = wrap_socket(sock, self.host)
    205             self._sock = BufferedSocket(sock, self.network_buffer_size)
    206

/Users/jakub/.virtualenvs/hyper-test/lib/python3.4/site-packages/hyper/http20/tls.py in wrap_socket(sock, server_hostname)
     33
     34     # the spec requires SNI support
---> 35     ssl_sock = _context.wrap_socket(sock, server_hostname=server_hostname)
     36     # Setting SSLContext.check_hostname to True only verifies that the
     37     # post-handshake servername matches that of the certificate. We also need to

/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/ssl.py in wrap_socket(self, sock, server_side, do_handshake_on_connect, suppress_ragged_eofs, server_hostname)
    362                          suppress_ragged_eofs=suppress_ragged_eofs,
    363                          server_hostname=server_hostname,
--> 364                          _context=self)
    365
    366     def set_npn_protocols(self, npn_protocols):

/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/ssl.py in __init__(self, sock, keyfile, certfile, server_side, cert_reqs, ssl_version, ca_certs, do_handshake_on_connect, family, type, proto, fileno, suppress_ragged_eofs, npn_protocols, ciphers, server_hostname, _context)
    576                         # non-blocking
    577                         raise ValueError("do_handshake_on_connect should not be specified for non-blocking sockets")
--> 578                     self.do_handshake()
    579
    580             except (OSError, ValueError):

/usr/local/Cellar/python3/3.4.2_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/ssl.py in do_handshake(self, block)
    803             if timeout == 0.0 and block:
    804                 self.settimeout(None)
--> 805             self._sslobj.do_handshake()
    806         finally:
    807             self.settimeout(timeout)

SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:600)

Lukasa · 2015-02-06T16:43:21Z

Aha, no. That's with old OpenSSL. With 1.0.2 I get the following:

cory@corymbp:tmp/ % /usr/local/Cellar/openssl/1.0.2/bin/openssl s_client -CAfile ~/Documents/Python/hyper/hyper/certs.pem -connect nghttp2.org:443
CONNECTED(00000003)
depth=2 C = BE, O = GlobalSign nv-sa, OU = Root CA, CN = GlobalSign Root CA
verify error:num=10:certificate has expired
notAfter=Jan 28 12:00:00 2014 GMT
---
Certificate chain
 0 s:/OU=Domain Control Validated/CN=*.nghttp2.org
   i:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
 1 s:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
   i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
---

tatsuhiro-t · 2015-02-06T16:46:16Z

Hello. nghttp2.org certificate expires coming April, but it should be ok until then.
So is this caused by old OpenSSL installation?

Lukasa · 2015-02-06T16:52:01Z

Arg I'm really confused. It seems to be a bug in OpenSSL 1.0.2. @jakubroztocil, are you running OpenSSL 1.0.2 as installed from Homebrew by any chance?

Observe:

cory@corymbp:tmp/ % openssl version                                            
OpenSSL 0.9.8za 5 Jun 2014
cory@corymbp:tmp/ % openssl s_client -CAfile ~/Documents/Python/hyper/hyper/certs.pem -connect nghttp2.org:443 
CONNECTED(00000003)
depth=2 /C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
verify return:1
depth=1 /C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
verify return:1
depth=0 /OU=Domain Control Validated/CN=*.nghttp2.org
verify return:1
---
Certificate chain
 0 s:/OU=Domain Control Validated/CN=*.nghttp2.org
   i:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
 1 s:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
   i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
---

cory@corymbp:tmp/ % /usr/local/Cellar/openssl/1.0.2/bin/openssl version        
OpenSSL 1.0.2 22 Jan 2015
cory@corymbp:tmp/ % /usr/local/Cellar/openssl/1.0.2/bin/openssl s_client -CAfile ~/Documents/Python/hyper/hyper/certs.pem -connect nghttp2.org:443
CONNECTED(00000003)
depth=2 C = BE, O = GlobalSign nv-sa, OU = Root CA, CN = GlobalSign Root CA
verify error:num=10:certificate has expired
notAfter=Jan 28 12:00:00 2014 GMT
---
Certificate chain
 0 s:/OU=Domain Control Validated/CN=*.nghttp2.org
   i:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
 1 s:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
   i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
---

jkbrzt · 2015-02-06T16:58:11Z

@Lukasa Yep:

$ /usr/local/Cellar/openssl/1.0.2/bin/openssl version
OpenSSL 1.0.2 22 Jan 2015

Lukasa · 2015-02-06T16:59:20Z

Interesting stuff...@jakubroztocil can you reproduce the test I just ran to confirm you see the same difference in behaviour between the system OpenSSL and 1.0.2? If you can, I think we may have stumbled into an OpenSSL 1.0.2 bug (or at least a Homebrew bug).

jkbrzt · 2015-02-06T17:03:31Z

@Lukasa

~ $ openssl version
OpenSSL 0.9.8zc 15 Oct 2014
~ $ openssl s_client -CAfile ~/.virtualenvs/hyper-test/lib/python3.4/site-packages/hyper/certs.pem -connect nghttp2.org:443
CONNECTED(00000003)
depth=2 /C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
verify return:1
depth=1 /C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
verify return:1
depth=0 /OU=Domain Control Validated/CN=*.nghttp2.org
verify return:1
---
Certificate chain
 0 s:/OU=Domain Control Validated/CN=*.nghttp2.org
   i:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
 1 s:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
   i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
---

~ $ /usr/local/Cellar/openssl/1.0.2/bin/openssl version
OpenSSL 1.0.2 22 Jan 2015
~ $
~ $ /usr/local/Cellar/openssl/1.0.2/bin/openssl s_client -CAfile ~/.virtualenvs/hyper-test/lib/python3.4/site-packages/hyper/certs.pem  -connect nghttp2.org:443
CONNECTED(00000003)
depth=2 C = BE, O = GlobalSign nv-sa, OU = Root CA, CN = GlobalSign Root CA
verify return:1
depth=1 C = BE, O = GlobalSign nv-sa, CN = GlobalSign Domain Validation CA - SHA256 - G2
verify return:1
depth=0 OU = Domain Control Validated, CN = *.nghttp2.org
verify return:1
---
Certificate chain
 0 s:/OU=Domain Control Validated/CN=*.nghttp2.org
   i:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
 1 s:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
   i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
---

Lukasa · 2015-02-06T17:04:11Z

Ah, interesting, so you don't reproduce it. Clearly my one is busted, I'll reinstall.

Lukasa · 2015-02-06T17:04:53Z

Actually, sorry @jakubroztocil, but can you test using the .pem file generated by running curl -o certs.pem https://mkcert.org/generate/?

jkbrzt · 2015-02-06T17:11:53Z

@Lukasa

$ /usr/local/Cellar/openssl/1.0.2/bin/openssl s_client -CAfile certs.pem  -connect nghttp2.org:443
CONNECTED(00000003)
depth=2 C = BE, O = GlobalSign nv-sa, OU = Root CA, CN = GlobalSign Root CA
verify return:1
depth=1 C = BE, O = GlobalSign nv-sa, CN = GlobalSign Domain Validation CA - SHA256 - G2
verify return:1
depth=0 OU = Domain Control Validated, CN = *.nghttp2.org
verify return:1
---
Certificate chain
 0 s:/OU=Domain Control Validated/CN=*.nghttp2.org
   i:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
 1 s:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign Domain Validation CA - SHA256 - G2
   i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
---

Lukasa · 2015-02-06T17:13:57Z

Interesting, so this is only happening to me, but it's very consistently happening to me. I've done a reinstall and that hasn't helped at all: neither has refreshing the certificate file.

Lukasa · 2015-02-06T17:15:44Z

Additionally, if I print out the certificate itself from my 1.0.2 there's clearly no problem with it:

cory@corymbp:tmp/ % /usr/local/Cellar/openssl/1.0.2/bin/openssl x509 -in cert.pem -text -noout 
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            04:00:00:00:00:01:15:4b:5a:c3:94
    Signature Algorithm: sha1WithRSAEncryption
        Issuer: C=BE, O=GlobalSign nv-sa, OU=Root CA, CN=GlobalSign Root CA
        Validity
            Not Before: Sep  1 12:00:00 1998 GMT
            Not After : Jan 28 12:00:00 2028 GMT
        Subject: C=BE, O=GlobalSign nv-sa, OU=Root CA, CN=GlobalSign Root CA

Lukasa · 2015-02-06T17:37:33Z

Unsurprisingly, that didn't work out...

Lukasa · 2015-02-06T17:48:44Z

Hmm. I'm going to ignore this for the moment.

@jakubroztocil Care to try testing against nghttp2, but replacing the hyper .pem file with the one you downloaded using curl? (The hyper .pem file should be inside the hyper package.)

t-8ch · 2015-02-06T18:03:45Z

@Lukasa The certificate you are seeing did exist: https://2014.globalsign.com/
Maybe openssl uses the OS X keychain?
Or have you tried grepping /usr/local/Cellar/openssl/1.0.2/ for part of the pem encoded cert?
openssl s_client -showcerts should show you it.

Lukasa · 2015-02-06T18:08:42Z

-showcerts doesn't show me the cert OpenSSL doesn't like. It shows me 0 and 1 in the cert chain, but not 2, which is the one that fails. Agree that it's possible it uses the OS X keychain though.

Lukasa · 2015-02-06T18:10:11Z

That said, the GlobalSign root CA I have in my keychain seems to match the working one.

t-8ch · 2015-02-06T18:16:51Z

Here is the pem for grepping: https://www.tbs-certificates.co.uk/FAQ/en/545.html

t-8ch · 2015-02-06T18:19:56Z

And: https://metaclassical.com/how-expired-root-certificates-broke-my-python-app-build/
This seems to confirm it: http://support.apple.com/en-us/HT202858

Lukasa · 2015-02-06T18:33:34Z

Hurrah, that worked @t-8ch! Once again I owe you big-time: if we're ever at the same conference I really have to buy you dinner.

Lukasa · 2015-02-06T18:36:03Z

Alrighty, so I'm running a travis build now that will hopefully pass most of its release tests (it won't pass Twitter because of silly Twitter-ness, but I'll try to find someone to talk to about that). If/when that happens I'll release a new hyper on PyPI for testing with @jakubroztocil's plugin.

jkbrzt · 2015-02-06T19:08:05Z

@Lukasa awesome

t2y · 2015-02-06T19:16:09Z

It means the plugin should be functional (to the same degree as hyper is), so you can now use it with HTTPie.

Thanks. It's really exciting. I tried, but an error happened.

httpie/httpie-http2#1

t2y · 2015-02-09T01:17:19Z

@Lukasa

I changed to emulate the CLI of Httpie in a limited way.

$ hyper -h
usage: hyper [-h] [--version] [--debug]
             [METHOD] URL [REQUEST_ITEM [REQUEST_ITEM ...]]

positional arguments:
  METHOD        
                The HTTP method to be used for the request
                (GET, POST, PUT, DELETE, ...).
  URL           
                The scheme defaults to 'https://' if the URL does not include one.
  REQUEST_ITEM  
                Optional key-value pairs to be included in the request.
                The separator used determines the type:

                ':' HTTP headers:

                    Referer:http://httpie.org  Cookie:foo=bar  User-Agent:bacon/1.0

                '==' URL parameters to be appended to the request URI:

                    search==hyper

                '=' Data fields to be serialized into a JSON object:

                    name=Hyper  language=Python  description='CLI HTTP client'

optional arguments:
  -h, --help    show this help message and exit
  --version     Show version and exit.
  --debug       Show debugging information (loglevel=DEBUG)

This hyper cli is for simple use or debugging. You can use hyper command as follows.

GET with parameters

NOTE: I haven't implemented the Httpie's escaping process since it's a bit of complexity. For example, \:, \= and \=\= are NOT escaped in hyper cli.

field-name-with\:colon=value

$ hyper GET https://nghttp2.org/httpbin/get x-test1:header1 x-test2:header2 p1==test1 p2==test2
{'args': {'p1': 'test1', 'p2': 'test2'},
 'headers': {'Connection': 'close',
             'Host': 'httpbin',
             'Via': '2.0 nghttpx',
             'X-Test1': 'header1',
             'X-Test2': 'header2'},
 'origin': '118.22.213.163',
 'url': 'https://httpbin/get?p2=test2&p1=test1'}

POST with data

Note: The postdata is serialized into a JSON object only. For simplicity, it doesn't have Content Types options (--json and --form). I'll add them if you want to switch. What do you think?

$ hyper POST https://nghttp2.org/httpbin/post name=hyper version=2.0
{'args': {},
 'data': '{"version": "2.0", "name": "hyper"}',
 'files': {},
 'form': {},
 'headers': {'Connection': 'close',
             'Content-Length': '35',
             'Content-Type': 'application/json; charset=utf-8',
             'Host': 'httpbin',
             'Via': '2.0 nghttpx'},
 'json': {'name': 'hyper', 'version': '2.0'},
 'origin': '118.22.213.163',
 'url': 'https://httpbin/post'}

Other options

$ hyper --version
0.2.0

$ hyper --debug ...
...
(show log.debug() info)
...

Lukasa · 2015-02-09T16:23:45Z

Fantastic! I'll grab this branch and give it a play, confirm everything looks good.

Lukasa · 2015-02-09T16:31:01Z

hyper/cli.py

+            setattr(info, attr, value)
+
+    if info.scheme == 'http':
+        info.port = 80


I think this will override a port set by the user by hand.

Ah, that's a bug. I'll fix it.

Lukasa · 2015-02-09T16:32:43Z

Alright, a couple of tiny nits, but this is almost ready to go!

t2y · 2015-02-11T17:25:11Z

@Lukasa is ready to merge? just ping.

Lukasa · 2015-02-11T22:58:59Z

Sorry, you're quite right, I lost track of this. =D

Add hyper as a Command Line Interface

Lukasa · 2015-02-11T22:59:17Z

LGTM, thanks so much @t2y! 🍰

t2y · 2015-02-12T02:24:55Z

No problem. Thank you, too! 😄

jkbrzt mentioned this pull request Feb 1, 2015

HTTP/2 support httpie/cli#298

Closed

jkbrzt added a commit to httpie/httpie-http2 that referenced this pull request Feb 6, 2015

Initial commit

11b0055

See: httpie/cli#298 python-hyper/hyper#82

t2y added 2 commits February 9, 2015 09:42

Added 'hyper' command as CLI

9700492

Changed to emulate the CLI of Httpie

a0d8050

t2y force-pushed the add-cli-tool branch from dac2596 to a0d8050 Compare February 9, 2015 00:45

Suppress logging for H2_NPN_PROTOCOLS

9d11301

Lukasa reviewed Feb 9, 2015
View reviewed changes

t2y added 2 commits February 10, 2015 01:52

Fixed to pass a port number specified by the user with http://

cd594bd

Moved to py2/py3 branches for importing sentence from urllib

b47a0e8

Lukasa added a commit that referenced this pull request Feb 11, 2015

Merge pull request #82 from t2y/add-cli-tool

7ae118c

Add hyper as a Command Line Interface

Lukasa merged commit 7ae118c into python-hyper:development Feb 11, 2015

t2y mentioned this pull request Feb 12, 2015

PROTOCOL_ERROR occurred when accessing twitter.com #84

Closed

t2y deleted the add-cli-tool branch April 12, 2015 06:04

Add hyper as a Command Line Interface #82

Add hyper as a Command Line Interface #82

Conversation

t2y commented Jan 31, 2015

sigmavirus24 commented Jan 31, 2015

t2y commented Jan 31, 2015

Lukasa commented Feb 1, 2015

t2y commented Feb 1, 2015

jkbrzt commented Feb 1, 2015

Lukasa commented Feb 1, 2015

jkbrzt commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

jkbrzt commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

jkbrzt commented Feb 6, 2015

Lukasa commented Feb 6, 2015

tatsuhiro-t commented Feb 6, 2015

Lukasa commented Feb 6, 2015

jkbrzt commented Feb 6, 2015

Lukasa commented Feb 6, 2015

jkbrzt commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

jkbrzt commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

t-8ch commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

t-8ch commented Feb 6, 2015

t-8ch commented Feb 6, 2015

Lukasa commented Feb 6, 2015

Lukasa commented Feb 6, 2015

jkbrzt commented Feb 6, 2015

t2y commented Feb 6, 2015

t2y commented Feb 9, 2015

Lukasa commented Feb 9, 2015

Lukasa Feb 9, 2015

Choose a reason for hiding this comment

t2y Feb 9, 2015

Choose a reason for hiding this comment

Lukasa commented Feb 9, 2015

t2y commented Feb 11, 2015

Lukasa commented Feb 11, 2015

Lukasa commented Feb 11, 2015

t2y commented Feb 12, 2015