Middleware for Downloader about core HOT 3 CLOSED

That would be pretty tricky to implement because it would essentially break the entire downloader pipeline.

Right now, each request is run through each RequestMiddleware first, so that any middleware can alter or drop the request before it gets sent. Then, the response is passed through each ResponseMiddleware. Adding a kind of middleware that takes a request and immediately returns a response would completely break this pattern, unfortunately.

A possible way to deal with this could be, extending the Request class to allow setting a Response on the request. The downloader could then check if the request already has a response set and simply return that response instead of sending the request. I think this is similar to how Symfony's kernel events work, too.

You could then implement a caching middleware by simply setting the cached response on the request inside a regular RequestMiddleware. The hypothetical API could look something like this:

class CachingMiddleware implements RequestMiddlewareInterface
{
    public function handleRequest(Request $request): Request
    {
        // assuming the cache returns `null` if no cached response exists, it's safe
        // to always set the result of `forRequest` on the request.
        $cachedResponse = $this->cache->forRequest($request);
        
        return $request->setResponse($cachedResponse);
    }
}

This would still allow the other middlewares to run as usual which is something I definitely want to preserve.

from core.

That's a great way of doing it, i'll work on adding that, Thanks!

from core.