Age | Commit message (Collapse) | Author |
|
|
|
Has a timer:sleep/1 though because there is currently no way
to wait for the TLS handshake to complete.
|
|
|
|
|
|
|
|
|
|
|
|
Now has a proper StreamRef given to it by the CONNECT stream.
|
|
|
|
|
|
|
|
Depending on timing the monitor may be applied after the Gun
process has started and stopped. In that case we run the test
again until timetrap_timeout.
|
|
|
|
|
|
|
|
|
|
Make sure we don't queue too much on the socket because in
that case Gun will just consume everything it's already got.
|
|
|
|
|
|
Also add a test for CONNECT to TLS via 2 TLS proxies.
|
|
|
|
Match inside the clause instead. This should make clearer
the occasional failure.
|
|
|
|
|
|
To attempt to fix a timetrap_timeout issue occuring sometimes.
I have little confidence about this fixing anything but it will
not hurt either.
|
|
Instead of timeouts, favor receiving events from the event
handler gun_test_event_h. Remove most other timeouts in particular
receive timeouts in favor of a Common Test timetrap timeout global
to this test suite of 30 seconds.
|
|
|
|
Turns out we can't rely on IPv4 being available if we set
the socket in IPv6 mode. Instead the origin is modified to
either setup IPv4 or IPv6 depending on the test's needs.
|
|
|
|
It seems that the retry behavior changed recently. It would
be better to retrieve the exact values and calculate how much
time we want to wait but that will do for now.
|
|
|
|
|
|
|
|
|
|
|
|
And make sure all HTTP/2 connection_error(s) result in a
gun_down message containing the error. In the preface case
we do not send a gun_error message (because there's no stream
open yet) and gun_down was always saying normal.
Also make sure the human readable reason is included in the
gun_error message, if any.
|
|
|
|
|
|
|
|
The reply_to option is also propagated when we switch protocols.
|
|
While at it the gun:info/1 function has been fixed to work
even when we are in the not_connected state, and the owner
is now also returned.
|
|
The auto-ping will at regular interval send a ping frame.
The silence_pings option defaults to true. It can be set
to false when the user needs to receive ping/pong frames.
|
|
|
|
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.
|
|
|
|
When Windows can't connect it retries 2 more times with
500ms wait in-between by default.
|
|
I'm not exactly sure why it works but it seems to be solid now.
I think the issue is around timeouts in the test and handler
being too close to one another.
|
|
It is better covered by the shutdown_SUITE.
|
|
Also correct various Socks related types. This commit also
adds a new gun:protocols/0 type as a simpler way of describing
preferred protocols. The protocol/opts tuple is also documented.
This commit also fixes an issue with the default value for the
preferred protocols when using CONNECT over TLS. It was
mistakenly not enabling http2 by default.
|
|
Also fix the multiple TLS proxies tests from the previous commit.
|