v0.20.0

Version v0.20.0, dated November 16, 2026, follows a code review of the core routing engine and the file component. Several HTTP routes can now share one port, nine findings are fixed, and a few visible behaviours change. Every component and observability module at v0.20.0 requires core v0.20.0.

Behaviour changes

  • HTTP routes share a port: consumers of one HTTPComponent whose URIs share a host:port now share a single listener and are told apart by their path, so From("http://0.0.0.0:8080/orders") and From("http://0.0.0.0:8080/health") can live in the same context. The port is released when the last of them stops, and a path already served on the port is rejected at Start. The consumer middleware now wraps each consumer’s handler: a path no consumer serves answers 404 without going through it.
  • Route start order: CamelContext.Start starts the routes consuming from direct: first, then the others, each group in declaration order. A consumer that routes an exchange as soon as it starts finds the direct: routes it calls already running.
  • file — relative move / moveFailed: a relative directory is resolved next to the consumed file (move=.done sends /data/in/a.txt to /data/in/.done/a.txt) instead of against the working directory of the process. Files lying in those directories are never consumed again, including with recursive=true.
  • file — backlog at startup: files already present in the directory are consumed by the consumer goroutine instead of from Start(), so a backlog no longer blocks the route and the context from starting.
  • ParseURI errors: the error no longer quotes the raw URI nor the offending fragment; it reports the redacted URI and the kind of failure (invalid URI "ftp://user:xxxxx@host/dir": invalid percent-encoding).

Fixes

  • HTTP Content-Type: a Content-Type the route sets to the value the request carried was dropped as an echoed inbound header, so a JSON API answering a JSON request replied text/plain. Content-Type is now exempt from the echo filter; a route that does not set it returns the request’s.
  • Loop and Stop(): the Stop EIP inside a loop was swallowed and the steps after the loop still ran. Stop() now ends routing of the exchange; any other stop signal (Filter, Sample…) still only ends the loop.
  • Resequencer context: buffered exchanges kept the context of the request that brought them and were delivered downstream with a cancelled context once that request was over. They are now delivered under the route’s lifecycle context.
  • Resequencer errors: the downstream failure of a buffered exchange was returned to whichever exchange triggered the delivery, failing (and redelivering) the wrong message. Only an exchange’s own failure is returned to it; the others are logged.
  • Idempotent Consumer: the key of a failed exchange was rolled back with the exchange context, often already cancelled, so a context-aware repository (Redis) kept the key and the redelivered message was dropped as a duplicate. The rollback now ignores the cancellation and is bounded to 30s.
  • Credential redaction: RedactURI returned a URI it could not parse unchanged, credentials included (a password holding a stray %). Such URIs are now masked textually.

Upgrading

  • A file route relying on a relative move / moveFailed resolved against the process working directory must switch to an absolute path.
  • Code matching the text of a ParseURI error must be updated.
  • An HTTP route that changes the body without setting Content-Type now returns the request’s Content-Type instead of a sniffed one: set it explicitly.

See the CHANGELOG for the full list of changes.