Skip to main content

MTE Relay Server v4.7 Release Notes

· 2 min read
Trevor Blackman
Trevor Blackman
Engineering Director

v4.7.0 adds standard forwarding headers and fixes a health check regression. Applies to MRS and MAR. Fully backwards compatible, no client changes required.

New​

  • X-Forwarded-Host is now set on every proxied request with the hostname the client originally requested. The relay always overwrites any client supplied value, so it is safe to trust.
  • FORWARD_HOST_HEADER env var controls this. Defaults to true; set false for pre-4.7.0 behavior.
  • Azure Container Apps template deploys Redis automatically when more than one replica is configured.

Improved​

  • X-Forwarded-Proto now carries http or https instead of the protocol version, and preserves a value set by an upstream load balancer.
  • X-Forwarded-For appends the client IP to an existing chain instead of dropping it.
  • On-prem images no longer emit marketplace billing log entries.
  • All images built with Go 1.26.5.

Fixed​

  • Health check regression: /api/mte-echo returned 400 when the Host header had no DOMAIN_MAP match, breaking load balancers that probe by IP. It now always returns 200.

Upgrading​

  • Redeploy with image tag 4.7.0. No client updates needed.
  • If an upstream misbehaves after upgrade, it may be reacting to the new X-Forwarded-Host header; set FORWARD_HOST_HEADER=false to revert.
  • Docs: Forwarding Headers and Version Compatibility.