Releases: ledgetech/lua-resty-http
Releases · ledgetech/lua-resty-http
v0.09
- Enhancement: Return a useful error if attempting to use a unix domain socket without a Host header.
- Bugfix: Don't attempt to keepalive a http 1.0 connection with no Connection header (Thanks @guanglinlv for the report).
- Bugfix: Only look for a single 's' in the scheme, and report the uri in any URI parsing errors.
- Bugfix: _handle_continue return value order didn't match with expectation. (Thanks @DilipSimha for the report).
v0.08
v0.07
Bugfix: Error handling for when buffer_size
isn't set when resuming the body_reader
.
Bugfix: Spaces now properly encoded in proxied URIs
Bugfix: A missing path now properly defaults to "/". Thanks @membphis
Bugfix: proxy_response
now checks the result of ngx.print
, and breaks the loop on error. Thanks @vovapi
Docs: Example code didn't require
the module. Thanks @zweite
v0.06
v0.05
- Headers are now normalised for case, both request headers passed in and response headers received (thanks @mikz for the report)
- Response headers received with multiple matching field names are now presented as a table of values rather than concatenated, as this caused issues with
Set-Cookie
and potentially other cases. Note that when evaluating headers you must now consider the type could either be atable
or astring
. (Thanks to @ngo for the original pull request / suggestion).
v0.04
- SSL cosocket support (thanks @hamishforbes).
- Improved error handling around pipelined responses and timeouts.
- Reset flags between requests so that an instance can safely be reused.
- More gracefully handle attempts to use the client body reader during a subrequest.
- Added
proxy_request
andproxy_response
functions. - Various documentation improvements.
v0.03
set_keepalive
now returns 2 if the connection was intentionally closed, to distinguish from actual errors.- Merged pull request from @hamishforbes adding support for "100 Continue" responses.
- Merged pull request from @hamishforbes allowing request bodies to optionally be an iterator function to stream in large bodies.
- Merged pull request from @hamishforbes adding
get_client_body_reader
utility, which returns an iterator for the current client upstream request body. res.body_reader
is now always a function, even if there is no body to be read.- Added
res.has_body
boolean flag. - Implemented streaming for HTTP 1.0 responses where no length is advertised. (Thanks @oikomi for the feature request).
- Fixed issue where body readers only honoured the initial chunk size. (Thanks @oikomi for the report).
- Added support for HTTP pipelining.