Releases: ducaale/xh
Releases Β· ducaale/xh
v0.23.0
Features
- Handle responses compressed in zstd format, see #364 (@zuisong)
- Suppress warnings when
-qq
flag is used, see #371 (@blyxxyz) - Add
--debug
option for logging and backtraces, see #371 (@blyxxyz) - Decode
content-disposition
andlocation
headers as UTF-8, see #375 (@zuisong) - Print headers as latin1, with the UTF-8 decoding also shown if applicable, see #377 (@blyxxyz)
- Print the actual reason phrase sent by the server instead of guessing it from the status code, see #377 (@blyxxyz)
Bug fixes
Other
v0.22.2
v0.22.0
Features
- Support http2-prior-knowledge, see #356 (@zuisong)
- Directly bind to interface name on supported platforms, see #359 (@ducaale)
- Enable stream when content-type is
text/event-stream
, see #360 (@zuisong) - Decode utf-8 encoded string when formatting non-streaming JSON response, see #361 (@zuisong)
Other
v0.21.0
v0.20.1
v0.19.4
v0.19.3
v0.19.2
Features
- Add
--interface
for binding to a local IP address or interface, see #307 (@ducaale) - Translate
--raw
flag when using--curl
, see #308 (@ducaale) - Support duplicate header keys in session files, see #313 (@ducaale)
- Support persisting cookies from multiple domains, see #314 (@ducaale)
- Control output formatting (JSON indent-level, header sorting, etc) via
--format-options
, see #318 (@Bnyro) and #319 (@ducaale)
Bug fixes
- Disable cURL's URL globbing, see #325 (@ducaale)
- Improve PATH handling in
install.ps1
, see #264 (@henno)
Other
v0.18.0
Features
- Support reading query param and header values from a file, see #288 (@ducaale)
- Highlight Syntax errors found while tokenizing a JSON path, see #260 (@ducaale)
- Support outputting the metadata of a response via
--meta
,--print=m
or-vv
, see #240 (@ducaale)
Bug fixes
- Fix panic when when parsing connection timeout, see #295 (@sorairolake)
Breaking changes
v0.17.0
Features
- Add support for nested json syntax, see #217 (@ducaale)
- Add Support for bearer auth in
.netrc
, see #267 (@porglezomp) - Add
--ipv4
and--ipv6
flags for forcing IPv4 and IPv6 respectively, see #276 (@zuisong)