gun.git/ebin, branch http2-websocket HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP. Initial success for h2 CONNECT -> https CONNECT -> https 2020-09-21T13:52:26+00:00 Loïc Hoguin essen@ninenines.eu 2020-09-18T15:01:25+00:00 8033850ab81ca0639489636bb8760d93900d4a80 






Refactor protocol handling via gun_protocols
2020-09-21T13:51:58+00:00

Loïc Hoguin
essen@ninenines.eu

2020-08-26T11:45:34+00:00

3de0604eec218996dad4db59c0cc96092cd7e0e7












First working HTTPS over secure HTTP/2
2020-09-21T13:51:57+00:00

Loïc Hoguin
essen@ninenines.eu

2020-08-19T15:24:27+00:00

ca68d184abbf7bd1030b2f2035cc66c13d08dd5d

Has a timer:sleep/1 though because there is currently no way
to wait for the TLS handshake to complete.





Has a timer:sleep/1 though because there is currently no way
to wait for the TLS handshake to complete.







Initial HTTP/2 CONNECT implementation
2020-09-21T13:51:46+00:00

Loïc Hoguin
essen@ninenines.eu

2020-07-16T12:56:45+00:00

a093bf88e1740e4f89937d84cd4d5b26cb5b4e80












Gun 2.0.0-pre.2
2020-03-25T11:21:47+00:00

Loïc Hoguin
essen@ninenines.eu

2020-03-25T11:21:47+00:00

d1d02a0ebc1a5d9852b7fe5216ac4ce628fb1744












Add the public suffix check to set_cookie
2020-03-05T10:33:59+00:00

Loïc Hoguin
essen@ninenines.eu

2020-03-04T15:50:16+00:00

a5ab2d83bb5e62e874d91fd6c86022db4baa908c












Initial implementation of the gun_cookies cookie store
2020-03-04T15:50:53+00:00

Loïc Hoguin
essen@ninenines.eu

2020-03-02T13:32:22+00:00

4e10d5c132a7b3a72f035eb1a993eb378b97ab1d












Gun 2.0.0-pre.1
2019-09-27T07:12:34+00:00

Loïc Hoguin
essen@ninenines.eu

2019-09-27T07:12:34+00:00

74ac4d209c86f64059b1eaa0e541eb7d26dd23a8












Initial support for raw send/recv operations
2019-09-24T11:21:26+00:00

Loïc Hoguin
essen@ninenines.eu

2019-09-24T11:21:26+00:00

a3c2edbb8c807717e2f10520c6cf1e77a62eab2e

Gun can now be used to send or receive arbitrary data in the
following scenarios:

* Directly after connecting to a server (this is not terribly
  useful but it works nevertheless due to the Gun architecture)

* After connecting through one or more Socks and/or HTTP proxies.
  This allows using Gun's proxy capabilities to access servers
  located beyond firewalls.

* After performing an HTTP/1.1 Upgrade. This allows using Gun
  to implement custom protocols that require upgrading from
  an HTTP/1.1 connection.

As there is still no support for HTTP/2 CONNECT for the time
being, there are no relevant streams attached to those use
cases and therefore the raw protocol currently expects users
to use 'undefined' as the StreamRef value. This is not a
final decision and will most likely produce a Dialyzer
warning at this time.





Gun can now be used to send or receive arbitrary data in the
following scenarios:

* Directly after connecting to a server (this is not terribly
  useful but it works nevertheless due to the Gun architecture)

* After connecting through one or more Socks and/or HTTP proxies.
  This allows using Gun's proxy capabilities to access servers
  located beyond firewalls.

* After performing an HTTP/1.1 Upgrade. This allows using Gun
  to implement custom protocols that require upgrading from
  an HTTP/1.1 connection.

As there is still no support for HTTP/2 CONNECT for the time
being, there are no relevant streams attached to those use
cases and therefore the raw protocol currently expects users
to use 'undefined' as the StreamRef value. This is not a
final decision and will most likely produce a Dialyzer
warning at this time.







Initial support for Socks5
2019-09-22T14:46:28+00:00

Loïc Hoguin
essen@ninenines.eu

2019-09-11T05:22:07+00:00

92fd84f61f95a0ecb8aea75c28207d81a9c6f94d