HoneyryderChuck
3ae18120d2
when users pass a Cookie header as option and plugin is enabled, the header will be parsed and managed by the jar
2021-07-16 09:52:21 +01:00
HoneyryderChuck
5604501d01
using the new OptionsMethods way for defining internal plugin options
2021-07-13 19:56:59 +01:00
HoneyryderChuck
383d624b71
changed all def_option from plugins to use the eval'ed string approach
2021-04-08 15:58:10 +01:00
HoneyryderChuck
cbfb5c968e
moving domain_name module to core httpx, as the punycode IDN translation will be needed at this layer
2020-11-07 01:34:48 +00:00
HoneyryderChuck
048501e940
adding and integrating the new cookie modules for: store, jar, cookie, and domain name
2020-11-04 00:32:01 +00:00
HoneyryderChuck
959429b386
improved cookies testing, to test also the array-of-cookie-hashes case; does not accept a string anymore, as besides untested, it wasn't working properly
2020-11-03 16:33:11 +00:00
HoneyryderChuck
1b068aca21
removing http-cookie
2020-11-03 16:33:11 +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
2e64db8a99
changed the way that options are attributed: use attribute=; this means that the setters defined in def_option will actually work this time
2020-03-10 18:58:31 +00:00
HoneyryderChuck
c744c431fb
fixed bug related to return on instance_exec evaluation, which was disallowed in that context
2020-02-29 18:14:13 +00:00
HoneyryderChuck
a4d83103d2
do not compare options objects by request-level options
2019-10-08 00:36:09 +01:00
HoneyryderChuck
26efb9daea
Blog
2019-05-24 14:10:31 +00:00
HoneyryderChuck
2da56ce9af
fix: keep connection alive if HTTP/1.1 and there is connection-related
...
header;
this was wrongly closing connections for HTTP/1.1 connections which
didn't send a "Connection" header; according to spec, the default is
"Keep-Alive", contrary to HTTP/1.0
2019-05-15 14:45:06 +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
11663ad914
simplifying cookies plugin by having less cookie response introspection (now there's a client cookies store)
2019-01-24 14:43:15 +00:00
HoneyryderChuck
26b54d2540
keeping a client-local cookie store per origin; setting the store when receiving a response; using it when building a request; also, using the request uri when retrieving the cookie jar, an added measure when a response returns cookies for different origins, potentially"
2019-01-04 11:56:02 +00:00
HoneyryderChuck
622188c0ab
updated rubocop, added a few changes...
2018-12-28 02:44:43 +00:00
HoneyryderChuck
79c7d72f2a
bumped rubocop to 0.54
2018-03-26 17:16:41 +01:00
HoneyryderChuck
2b1ab8b6b6
rubocop auto-corrections according to some basic rules for now
2018-01-28 22:33:41 +00:00
HoneyryderChuck
5ee94bbc98
added test which loads the cookies from the response and passes it to the next request; added the functionality also, along with the cookie jar
2017-12-19 12:59:03 +02:00
HoneyryderChuck
1c507545c1
cookies might be nil (in fact, the default options won't be the same when expanding the options, think about this for a while
2017-12-19 11:48:51 +02:00
HoneyryderChuck
6ed620caff
added the cookie plugin, with the first test: passing the cookie in the options
2017-12-18 18:09:30 +02:00
