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

Age	Commit message (Collapse)	Author
2020-11-12	Return 'undefined' for raw\|socks origin_scheme where applicable	Loïc Hoguin

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

2020-11-06	Fix IsFin mismatch in HTTP/2 CONNECT response	Loïc Hoguin
	The response ends when the tunnel is established, even if the stream itself does not. The data coming in on the stream after is not part of the response. This makes both HTTP/1.1 and HTTP/2 send 'fin' to successful CONNECT responses.
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	Rename the 3-arity gun_socks_up to gun_tunnel_up	Loïc Hoguin

2020-09-21	Add gun_tunnel_up message to HTTP/2 CONNECT	Loïc Hoguin

2020-09-21	HTTP/2 over HTTP/2 CONNECT	Loïc Hoguin

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.
2020-09-21	Make gun:stream_info/2 return intermediaries for HTTP/2 CONNECT	Loïc Hoguin

2020-09-21	Initial HTTP/2 CONNECT implementation	Loïc Hoguin

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.