gun.git - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.

Age	Commit message (Collapse)	Author
2023-01-23	Update copyright lines in preparation for release	Loïc Hoguin

2022-11-14	Implement gun_raw:down/1, gun_raw:update_flow/4	Denys Knertser
	Loïc: I have reworded a couple things and reordered the tests. It would be great to also test these things over proxies.
2022-10-24	Handle send errors	Viktor Söderqvist

2022-08-30	Make Protocol:init/4 return an ok-tuple	Viktor Söderqvist
	This is a preparation for allowing init/4 to return an ok or an error tuple.
2022-03-08	Return commands instead of state in remaining callbacks	Viktor Söderqvist

2020-11-12	Update copyright years	Loïc Hoguin

2020-10-21	Fix cookie handling when tunnel and origin schemes mismatch	Loïc Hoguin
	The cookie_ignore_informational has been moved to http_opts and http2_opts. Also fix an issue when using 'protocols' in gun:open. When connecting via TLS the protocol's options were discarded.
2020-09-21	Add a gun:stream_ref() type and fix Dialyzer	Loïc Hoguin

2020-09-21	Replace gun_tunnel_up/3 message with /4 variant	Loïc Hoguin
	Also fixes all the tests. Lots of work remain around protocols (how best to pass the base stream_ref to them? maybe the current solution, maybe a new argument to Protocol:init) and strengthen the concept of stream_ref, at least with its own type.
2020-09-21	Improve HTTP/2 CONNECT to non-HTTP origin	Loïc Hoguin
	Now has a proper StreamRef given to it by the CONNECT stream.
2019-09-26	Add reply_to option to ws_upgrade; remove notowner entirely	Loïc Hoguin
	The reply_to option is also propagated when we switch protocols.
2019-09-24	Initial support for raw send/recv operations	Loïc Hoguin
	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.