1 From 81bf140583f7b7bf13cc8dd522e1ca2aba873fc4 Mon Sep 17 00:00:00 2001
2 From: Martin Negyokru <negyokru@inf.u-szeged.hu>
3 Date: Mon, 3 Oct 2022 12:20:00 +0200
4 Subject: Do not intercept websocket connection when there is no associated
7 This fix is based on chrome's implementation.
10 Change-Id: If042e4156b8a4bdb27a210c4db94e3a6198aed7d
11 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
12 (cherry picked from commit 64b7da9dab82713fdcb2e03d8a2715421eae5685)
13 Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
15 src/core/content_browser_client_qt.cpp | 3 +--
16 1 file changed, 1 insertion(+), 2 deletions(-)
18 diff --git a/src/core/content_browser_client_qt.cpp b/src/core/content_browser_client_qt.cpp
19 index 020ae916a..99a3aa3f4 100644
20 --- a/src/core/content_browser_client_qt.cpp
21 +++ b/src/core/content_browser_client_qt.cpp
22 @@ -1237,8 +1237,7 @@ ContentBrowserClientQt::WillCreateURLLoaderRequestInterceptors(content::Navigati
24 bool ContentBrowserClientQt::WillInterceptWebSocket(content::RenderFrameHost *frame)
27 - return true; // It is probably not worth it to only intercept when interceptors are installed
28 + return frame != nullptr;
31 QWebEngineUrlRequestInterceptor *getProfileInterceptorFromFrame(content::RenderFrameHost *frame)