Route by header or path, renamed route keys, and TLS certificate rotation fixes.
Breaking
New
- Routes can match by path, by header, or by both. Header matches are checked first, then the longest path
- The access log has a new
header_matchfield showing which header matched the route nocleye checkreports every new rule with where it is and how to fix it- New warnings for a route that removes
AuthorizationorCookie, and forAddHeadersetting the header the route matched on AddPathPrefixis validated: it must start with/and not end with/
Improved
Fixes
- Fix TLS certificate rotation detection: a renewed certificate is picked up within 10 seconds, no restart needed. An invalid new certificate is ignored and the previous one keeps being served
HeaderRule.Setnow rejectsX-Nocleye-*headers, headers managed by HTTP or the proxy, and values with control characters. Identity headers such asX-User-IdandX-Tenantcan still be set- A route can no longer match on
Hostor on an invalid header name, which would silently never match
