.../big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/modules/big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php b/core/modules/big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php
index 2c644ee..ce31c15 100644
--- a/core/modules/big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php
+++ b/core/modules/big_pipe/src/EventSubscriber/HtmlResponseBigPipeSubscriber.php
@@ -99,7 +99,7 @@ public function onRespond(FilterResponseEvent $event) {
     // A BigPipe response can never be cached, because it is intended for a
     // single user.
     // @see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1
-    $response->setPrivate();
+    $big_pipe_response->setPrivate();
 
     // Inform surrogates how they should handle BigPipe responses:
     // - "no-store" specifies that the response should not be stored in cache;
@@ -109,7 +109,7 @@ public function onRespond(FilterResponseEvent $event) {
     //   should not process at all, and in fact, they should not even buffer it
     //   at all.
     // @see http://www.w3.org/TR/edge-arch/
-    $response->headers->set('Surrogate-Control', 'no-store, content="BigPipe/1.0"');
+    $big_pipe_response->headers->set('Surrogate-Control', 'no-store, content="BigPipe/1.0"');
 
     // Add header to support streaming on NGINX + php-fpm (nginx >= 1.5.6).
     $big_pipe_response->headers->set('X-Accel-Buffering', 'no');