Crawlers

The extension uses crawlers to visit all URLs configured for cache warmup. While visiting a URL, the appropriate page cache gets warmed. Learn more about which crawlers are available by default and how to implement a custom crawler on this page.

interface Crawler
Fully qualified name
\EliasHaeussler\CacheWarmup\Crawler\Crawler

Interface for crawlers used to crawl and warm up URLs.

crawl ( $urls)

Crawl a given list of URLs.

param array $urls

List of URLs to be crawled.

returntype

EliasHaeussler\CacheWarmup\Result\CacheWarmupResult

Default crawlers

The extension ships with two default crawlers:

  • \EliasHaeussler\Typo3Warming\Crawler\ConcurrentUserAgentCrawler: Used for cache warmup triggered within the TYPO3 backend
  • \EliasHaeussler\Typo3Warming\Crawler\OutputtingUserAgentCrawler: Used for cache warmup executed from the command-line

Both crawlers use a custom User-Agent header for all warmup requests. By using this custom header, it is possible to exclude warmup requests from the statistics of analysis tools, for example. The header is generated by a HMAC hash of the string TYPO3/tx_warming_crawler.

The generated header value can be copied form the cache warmup modal in the TYPO3 backend. Alternatively, a command warming:showuseragent is available which can be used to read the current User-Agent header.

Implement a custom crawler

Available interfaces

The actual cache warmup is done via the library eliashaeussler/cache-warmup. It provides \EliasHaeussler\CacheWarmup\Crawler\Crawler, which must be implemented when developing your own crawler. There is also a \EliasHaeussler\CacheWarmup\Crawler\VerboseCrawler that redirects user-oriented output to an instance of \Symfony\Component\Console\Output\OutputInterface.

Configurable crawlers

Custom crawlers can also implement \EliasHaeussler\CacheWarmup\Crawler\ConfigurableCrawler, allowing users to configure warmup requests themselves.

Logging crawlers

Crawling results can be logged using a dedicated PSR-3 logger. For this, crawlers must implement \EliasHaeussler\CacheWarmup\Crawler\LoggingCrawler and inject an appropriate PSR-3 logger. In TYPO3 context, this is mostly done using TYPO3's log manager. Read more about logging in the official documentation.

Stoppable crawlers

Crawlers implementing \EliasHaeussler\CacheWarmup\Crawler\StoppableCrawler may cancel a cache warmup prematurely if any crawling failure occurs. This can be especially useful for validation purposes to check whether any page within an XML sitemap is inaccessible or failing.

Streamable crawlers

When running cache warmup from the TYPO3 backend, the current crawling progress is streamed to the cache warmup progress modal. However, this is only supported for crawlers implementing \EliasHaeussler\Typo3Warming\Crawler\StreamableCrawler.

Those crawlers will then get a \EliasHaeussler\SSE\Stream\EventStream injected. It can be used to send events to the current event stream. The following events are currently available:

  • \EliasHaeussler\Typo3Warming\Http\Message\Event\WarmupFinishedEvent
  • \EliasHaeussler\Typo3Warming\Http\Message\Event\WarmupProgressEvent

By default, when implementing a streamable crawler, there's no need to trigger these events by your own. Instead, it's better to use the provided \EliasHaeussler\Typo3Warming\Http\Message\Handler\StreamResponseHandler which takes care of sending appropriate events.

Steps to implement a new crawler

  1. Create a new crawler

    The new crawler must implement at least one of the following interfaces:

    • \EliasHaeussler\CacheWarmup\Crawler\Crawler
    • \EliasHaeussler\CacheWarmup\Crawler\ConfigurableCrawler
    • \EliasHaeussler\CacheWarmup\Crawler\LoggingCrawler
    • \EliasHaeussler\CacheWarmup\Crawler\StoppableCrawler
    • \EliasHaeussler\CacheWarmup\Crawler\VerboseCrawler
    • \EliasHaeussler\Typo3Warming\Crawler\StreamableCrawler

  2. Configure the new crawler

    Add the new crawler to the extension configuration. Note that you should configure either the crawler or verboseCrawler option, depending on what interface you have implemented.

  3. Flush system caches

    Finally, flush all system caches to ensure the correct crawler class is used for further cache warmup requests.