Due to a customer report yesterday evening about log messages, we were quickly able to find and fix two bugs.
* Bugfix: on Servebolt Linux 8/php 8.3+ the purge candidate urls were filtering too many out of being purgable.
* Bugfix: False positive error in logs when logged in that the Cache-Tag headers could not be sent. Cache-Tags should never be present for logged in users.
* Bugfix: on Servebolt Linux 8/php 8.3+ the purge candidate urls were filtering too many out of being purgable.
* Bugfix: False positive error in logs when logged in that the Cache-Tag headers could not be sent. Cache-Tags should never be present for logged in users.
The problems were brought about by 2 things.
- We added filtering to urls that would be purged. Worked fine on most systems, but with PHP 8.3+ it became greedy, excluding most purge candidates. We removed the filters that were too greedy, keeping it to only exclude urls from purging if they contain /index.php/ or /wp-admin/. If /index.php/ is in the url, permalinks are broken and should not be cached, and if /wp-admin/ is in a candidate url it will not be cached by either Accelerated Domains or Servebolt CDN.
- We moved some things around to give better error reporting in the last version, but did not test it logged in. It was only against logged in sessions that the ErrorLog message was set. Now if logged in or there is 0 headers to apply it will not give the error.
