fix: Do not try to set HTTP response code on already closed connection

This avoids a PHP warning in the logs about trying to set the response
 code while the output already started. It’s useless to try to print an
 error page anyway in this situation because the connection was closed
 already.

Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>

diff --git a/lib/private/legacy/OC_Files.php b/lib/private/legacy/OC_Files.php
index 1b2f83941c87ab5062638bd17c8368ccf877b767..b8eb6fe1ed02090f5a52d1c6ac63ebfbee06a370 100644 (file)
--- a/lib/private/legacy/OC_Files.php
+++ b/lib/private/legacy/OC_Files.php
@@ -233,7 +233,8 @@ class OC_Files {
                } catch (\OCP\Files\ConnectionLostException $ex) {
                        self::unlockAllTheFiles($dir, $files, $getType, $view, $filename);
                        OC::$server->getLogger()->logException($ex, ['level' => \OCP\ILogger::DEBUG]);
-                       \OC_Template::printErrorPage('Connection lost', $ex->getMessage(), 200);
+                       /* We do not print anything here, the connection is already closed */
+                       die();
                } catch (\Exception $ex) {
                        self::unlockAllTheFiles($dir, $files, $getType, $view, $filename);
                        OC::$server->getLogger()->logException($ex);