diff options
| author | Michal Klocek <michal.klocek@qt.io> | 2023-09-13 13:54:12 +0200 |
|---|---|---|
| committer | Michal Klocek <michal.klocek@qt.io> | 2023-10-12 14:32:02 +0000 |
| commit | f46e2f2d681f826c75637876e5df786664232ab1 (patch) | |
| tree | f9bf03dfd795e4cca563e8d0b66dbad6e7bf84d7 /src/core/profile_adapter.cpp | |
| parent | b05fab3c778ebaa9de7aa910342401012e03576d (diff) | |
Fix corrupted load/fetch state on start up in case of NoCache
The NoCache option on profile schedules clearHttpCache task. However,
this task will run later and BrowsingDataRemover will break
current network context mojo pipes. Network context will be recreated
eventually but all the load/request states are gone.
Do not delete explicitly cache on NoCache setting, which was
undocumented 'feature' anyway. Let the user take
care of that. Note doing reset network context on startup is fine as it
is not delayed.
[ChangeLog][WebEngineCore][WebEngineProfile] Switching profile to NoCache
do not longer implicitly removes cache from old data store.
Pick-to: 6.6 6.5
Task-number: QTBUG-116478
Change-Id: Ibd108d4ce7392349304df9f606738dc14dba36a0
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
Diffstat (limited to 'src/core/profile_adapter.cpp')
| -rw-r--r-- | src/core/profile_adapter.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/core/profile_adapter.cpp b/src/core/profile_adapter.cpp index 42c419efc..8767f4e0d 100644 --- a/src/core/profile_adapter.cpp +++ b/src/core/profile_adapter.cpp @@ -345,8 +345,6 @@ void ProfileAdapter::setHttpCacheType(ProfileAdapter::HttpCacheType newhttpCache return; if (!m_offTheRecord && !m_profile->m_profileIOData->isClearHttpCacheInProgress()) { m_profile->m_profileIOData->resetNetworkContext(); - if (m_httpCacheType == NoCache) - clearHttpCache(); } } |