.../big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/modules/big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php b/core/modules/big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php
index 31d1278..2fd40fd 100644
--- a/core/modules/big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php
+++ b/core/modules/big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php
@@ -58,7 +58,7 @@ public function onRespondEarly(FilterResponseEvent $event) {
     // It does not make sense to have BigPipe responses for subrequests. BigPipe
     // is never useful internally in Drupal, only externally towards end users.
     $response = $event->getResponse();
-    $is_eligible = $event->isMasterRequest() && $response instanceof HtmlResponse;
+    $is_eligible = $response instanceof HtmlResponse;
     $event->getRequest()->attributes->set(self::ATTRIBUTE_ELIGIBLE, $is_eligible);
     if (!$is_eligible) {
       return;