Releases: ledgetech/ledge
Releases · ledgetech/ledge
v1.17
- Background revalidation jobs can now pass headers from the originating parent request. These are configurable, with the defaults being
Authorization
andCookie
, and can also be modified be binding to theset_revalidation_headers
event. - Add event to modify parent headers passed into background revalidate
- PURGE jobs now heartbeat between SCANs
- Explicitly flush yielded data before each esi:include
v1.16
- Moved wildcard purges to a background job, managed by Qless. This means that wildcard purges will always return 200, regardless of whether there was anything to purge or not.
- Wildcard purges now attempt to use a Redis slave for SCAN commands, if available.
- Qless jobs are now tagged with their type, as
purge
,revalidate
orcollect_entity
. This helps tracking. - Qless jobs now have different priorities:
collect_entity
is highest,revalidate
second, andpurge
lowest. max_stale
config setting now ignores response headers in deciding if it's ok to serve stale (essentially it overrides). Though they are still honoured when the client issues aCache-Control: max-stale=n
header.- Background revalidation now has SSL support.
v1.15
- Bugfix: Whitespace in esi:include tags wasn't handled. Thanks @hamishforbes.