[Webkit-unassigned] [Bug 29631] New: Online whitelist wildcard flag not allowing access to non-manifest resources

Tue Sep 22 01:52:09 PDT 2009

https://bugs.webkit.org/show_bug.cgi?id=29631

           Summary: Online whitelist wildcard flag not allowing access to
                    non-manifest resources
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh
        OS/Version: Mac OS X 10.6
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jstark at jonathanstark.com

Created an attachment (id=39908)
 --> (https://bugs.webkit.org/attachment.cgi?id=39908)
Archive of a few text files that demo the bug described

I apologize in advance if this is the wrong place to report this bug (I have
also reported it at Apple.com). 

This bug seems to be specific to Mobile Safari on iPhone OS 3.1 - I can't
reproduce it in WebKit Version 4.0.3 (6531.9, r48592) on Mac OS X 10.6.1.

In a nutshell, resources that are not referenced in a cache manifest file are
not loaded, even when an asterisk exists in the network section of the manifest
file. 

So, given a host file "index.html"...

<!DOCTYPE HTML>
<html manifest="test.manifest">
    <head>
        <link rel="stylesheet" href="screen.css" type="text/css" media="screen"
title="no title" charset="utf-8" />
    </head>
    <body>
        <h1>Hello!</h1>
    </body>
</html>

...and a manifest file "test.manifest"...

CACHE MANIFEST

CACHE:

NETWORK:
*

... I would expect screen.css to load when a user browses to index.html, and in
fact, that is what happens on the desktop. However, when the user browses to
index.html in Mobile Safari, the CSS is not loaded. 

Perhaps I am misunderstanding how cache manifest is supposed to work, but I
would assume that it should be consistent across these two platforms. 

Thanks,
j

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.