Tags from libwebsockets

v3.2.3

2020-05-06T17:25:37Z

v4.0.7: h2: client: do not apply host header if h2 negotiated by alpn

2020-05-05T11:48:08Z

h2: client: do not apply host header if h2 negotiated by alpn

If client negotiated over alpn, it will have done SNI. Some
peers like youtube.com reject with 400 if you sent a host: as
well.

v4.0.6

2020-05-04T16:03:08Z

v4.0.5: h2: client sid: must be allocated at header send

2020-05-04T13:37:37Z

h2: client sid: must be allocated at header send

There is no way to allocate a client wsi mux sid before the headers are
send, because we don't know the order in which new wsi headers will be sent
and so seen by the peer.

The peer inisists that sid indexes only increase... we cannot allocat sids
monotonically at the client and then send them disordered...

v4.0.4: strexp: reset out offset each time

2020-04-30T19:32:30Z

strexp: reset out offset each time

A second strexp mustn't inherit the offset of the first, completed one

v4.0.3: BoringSSL: provide X509_VERYFY_PARAM_Set1_host length

2020-04-30T04:23:12Z

BoringSSL: provide X509_VERYFY_PARAM_Set1_host length

X509_VERYFY_PARAM_Set1_host of openSSL allows the third argument, which
is the length of the hostname string, to be 0. Then, it assumes hostname
is a null-terminated C string. BoringSSL enforces the actual length to
be specified, and the hostname string should end with a null char.

Just provide the length, making both OpenSSL and BoringSSL happy.

v4.0.2

2020-04-29T10:34:05Z

v4.0.1

2020-03-10T07:57:43Z

v4.0.0

2020-03-06T10:44:23Z

v3.2.2

2020-01-17T12:38:42Z