[Bug 20854] New: appcache : fallback entries need clarification on duplicates

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20854

            Bug ID: 20854
           Summary: appcache : fallback entries need clarification on
                    duplicates
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: l.laurent.p@gmail.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

Hi

The reference
http://www.w3.org/html/wg/drafts/html/master/browsers.html#concept-appcache-fallback
needs to mention that fallback entries can't contain uri duplicates.

Use case : on first manifest visit, cookieless user agent may use url rewriting
for resources, ie use a ";jsessionid=" trail or some other kind of session
parameter. The uri + session trail seems to be the cache key at least on iOS
devices.

The following manifest will cause Chrome 24 to fail loading the manifest, with
a cryptic "Application Cache Error event: Failed to commit new cache to
storage" error message : 

CACHE MANIFEST
/foo.php

FALLBACK:
/ /fallback.php
/ /fallback.php?sessionid=1234

NETWORK:
*

This will fail because of the duplicate /fallback.php line. Removing the second
one with ?sessionid fixes the problem. I believe Chrome does not know which
fallback line to use.

Thanks

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 2 February 2013 11:12:39 UTC