Bug 128557 - Bring third-party app cache blocking behavior in line with private browsing app cache blocking behavior
Summary: Bring third-party app cache blocking behavior in line with private browsing a...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Vicki Pfau
URL:
Keywords: InRadar
Depends on:
Blocks: 131263
  Show dependency tree / graph
 
Reported: 2014-02-10 15:33 PST by Vicki Pfau
Modified: 2014-04-18 12:33 PDT (History)
4 users (show)

See Also:

Attachments
Patch (13.27 KB, patch)
2014-02-10 19:26 PST, Vicki Pfau 		ap: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vicki Pfau 2014-02-10 15:33:12 PST 
As of r163823, in private browsing mode, application cache is blocked with a specific behavior (raising errors when blocking the cache). However, the third-party data blocking approach silently fails. We should bring the third-party data blocking approach in line with the new behavior for application cache blocking.
Comment 1 Vicki Pfau 2014-02-10 19:11:26 PST 
<rdar://problem/16033265>
Comment 2 Vicki Pfau 2014-02-10 19:26:14 PST 
Created attachment 223792 [details]
Patch
Comment 3 Vicki Pfau 2014-02-11 15:03:05 PST 
Committed r163914: <http://trac.webkit.org/changeset/163914>
Comment 4 David Kilzer (:ddkilzer) 2014-04-18 12:33:14 PDT 
This caused the following regression:

REGRESSION (r163914): Application cache cannot be used in main frame
https://bugs.webkit.org/show_bug.cgi?id=131263