HoneyryderChuck
fab44b5993
verifyig error responses annd deltas using internal methods
2021-01-05 18:57:39 +00:00
HoneyryderChuck
bb310dc106
making the connection ping when keep alive timeout is exceeded; this way if the connection is still available, it's reused
2020-05-03 16:28:58 +01:00
HoneyryderChuck
f6475009fe
now that the timer interval is used in the selector, make sure that timeouts from selecting are properly reflected as total timeouts when they are
2020-04-12 03:32:04 +01:00
HoneyryderChuck
fef2d78382
show what happened if not the timeout
2020-04-05 04:26:43 +01:00
HoneyryderChuck
bc65c44e21
do not run keep alive test for ruby < 2.3, as our HTTP/1 server does not support keep alive
2020-03-30 02:31:22 +01:00
HoneyryderChuck
36134dd826
added test for keep alive timeout
2020-03-30 01:13:58 +01:00
HoneyryderChuck
adc0e71c7f
commenting connect timeout test (not there yet)
2020-03-15 02:18:24 +00:00
HoneyryderChuck
89fde80f10
reenabled timeout tests again
2020-03-14 22:42:02 +00:00
HoneyryderChuck
108d9257c8
added support for HTTP#with_ methods
...
these will reapply options accordingly (i.e. HTTPX.with_headers(...)).
Because we now have these, HTTPX.headers and HTTPX.timeout have been
deprecated.
2020-03-10 18:58:31 +00:00
HoneyryderChuck
731db5691b
moving resolver tests to the mainline requests
2020-02-02 09:41:30 +01:00
HoneyryderChuck
07c22470a9
added regression test for the reported failure
2020-01-26 20:39:34 +00:00
HoneyryderChuck
ae3cbac91d
disabling connect timeout for CI
2020-01-12 21:42:12 +00:00
HoneyryderChuck
4dd40464f6
connect error: give time to the server to boot up, just in case
2020-01-11 13:24:39 +00:00
HoneyryderChuck
e4e04e9fe8
setting the connect timeout port as envvar
2020-01-11 13:19:21 +00:00
HoneyryderChuck
066ff44762
moved timeout tests to the session, as they are not supposed to be differentiated in http/https terms
2019-12-31 01:57:00 +00:00
HoneyryderChuck
ae859f743f
request exposes options: this allows responses to be created with the proper set of options, instead of the connection options, which is wrong
2019-05-06 11:56:11 +00:00
HoneyryderChuck
ce9f55c96e
pool: allowing it to load more than one resolver per pool, depending on connection conditions; still reusing it whenever possible (right now, per type, which is still wrong, if we want to connect, let's say, to more than a different DNS server with the same type)
2019-04-27 15:51:37 +00:00
HoneyryderChuck
c1c0c536eb
Client -> Session (signal this as deprecation, as this is public API
2019-03-16 16:32:33 +00:00
HoneyryderChuck
05543d12f6
not a TODO anymore
2019-03-16 16:24:44 +00:00
