Protocol errors for example uses (curl, due to HTTP2)

[shhac]

• Newer versions of curl support the HTTP2 feature
• Trying to connect to Agile CRM's dev api will result in ALPN, offering h2, which is then accepted ALPN, server accepted to use h2 so a HTTP/2 connection is negotiated
• This stream then dies almost straight after sending some headers

* HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, Client hello (1):
curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)

---

To use the examples, you need to force a non-h2 connection using an extra flag, e.g. --http1.1 so h2 is not attempted