Releases: denschub/camo-rs
camo-rs 1.1.6
This version does not contain any functional changes. It only updates third-party dependencies.
camo-rs 1.1.5
This version does not contain any functional changes. It only updates third-party dependencies. Included in those is an update for h2
to resolve a potential Denial of Service attack when dealing with http/2 upstream connections.
camo-rs 1.1.4
This release targets users of the official container image. If you're running camo-rs
outside of a containerized environment, feel free to ignore this.
Full changes
- Official Docker image: Drop
libjemalloc
. There have been two reports about increased idle memory usage when usinglibjemalloc
, havingcamo-rs
sit above the 100 MiB mark. While the allocator would release that memory under memory pressure, this application isn't designed for a usage where allocator performance is important anyway, so let's move back to the default system allocator for the official container image.
camo-rs 1.1.3
This version does not contain any functional changes. It only updates third-party dependencies.
camo-rs 1.1.2
This version does not contain any functional changes. It only updates third-party dependencies.
camo-rs 1.1.1
This version does not contain any functional changes. It only updates third-party dependencies.
camo-rs 1.1.0
- Switch from OpenSSL-bindings to Rustls, to avoid incompatibilities between OpenSSL 1.x and 3.x (looking at you, Canonical)...
- Switched back to Ubuntu 20.04 to build the binaries that are attached to GitHub releases, as the glibc in 22.04 is a bit too new for most folks...
camo-rs 1.0.0
This is the first release version of camo-rs
, so there are no breaking changes to any previous stable release!
For people running a 0.x prerelease, these are the breaking changes between the latest pre-release and this stable release:
- For boolean settings like
CAMO_ALLOW_IMAGE
, you have to explicitly settrue
orfalse
as values, and other values will be rejected as invalid. The previous behavior, where any specified value (likeyes
or confusingly evenno
) would be parsed astrue
has been removed. Omitting those fields will, however, still set them tofalse
by default.
camo-rs 0.3.0
- You can now set the log output level with
--log-level
/CAMO_LOG_LEVEL
, and the log output format with--log-format
/CAMO_LOG_FORMAT
. Please see the documentation for full details!
camo-rs 0.2.0
camo-rs
now refuses to start if no content-types are allowed. Before that, Camo would start up just fine, but reject everything, which can be confusing.- When receiving a status code outside the expected range (
[200..399]
), Camo will still reject that request, but will pass the upstream status code to the client. - Even with
RUST_LOG=warn
, the log will still contain the encoded digest, target, and - if available - the decoded and validated target URL. This makes debugging production setups easier.