sharpetronics/httpx
1
0
Fork 0
mirror of https://github.com/HoneyryderChuck/httpx.git synced 2025-08-10 00:01:27 -04:00
Code Issues Projects Releases Wiki Activity
httpx/lib/httpx
History
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
..
adapters
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
connection
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
io
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
parser
updated rubocop, added a few changes...
2018-12-28 02:44:43 +00:00
plugins
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
resolver
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
transcoder
transcoder: handle #length as #size
2019-03-16 02:40:25 +00:00
altsvc.rb
updated rubocop, added a few changes...
2018-12-28 02:44:43 +00:00
buffer.rb
Non-Blocking DNS
2018-08-29 10:23:08 +00:00
callbacks.rb
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
chainable.rb
Client -> Session (signal this as deprecation, as this is public API
2019-03-16 16:32:33 +00:00
connection.rb
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
errors.rb
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
extensions.rb
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
headers.rb
removed inconsequent TODOs
2019-03-16 18:03:08 +00:00
io.rb
Non-Blocking DNS
2018-08-29 10:23:08 +00:00
loggable.rb
test if log stream responds to #isatty (thereby fulfilling the log requirement 'must implement #<<' (Closes #45)
2019-04-09 16:59:17 +01:00
options.rb
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
pool.rb
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
registry.rb
updated rubocop, added a few changes...
2018-12-28 02:44:43 +00:00
request.rb
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
resolver.rb
updated rubocop, added a few changes...
2018-12-28 02:44:43 +00:00
response.rb
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
selector.rb
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
session.rb
fix: keep connection alive if HTTP/1.1 and there is connection-related
2019-05-15 14:45:06 +00:00
timeout.rb
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
transcoder.rb
added support for chunking requests (sadly, not being able to test it well...)
2017-12-09 01:11:24 +00:00
version.rb
bumping to 0.3.1, adding docs
2018-12-27 16:25:40 +00:00