This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16868 - appcache: How to deal with redundant slashes in url of resources listed in manifest file?
Summary: appcache: How to deal with redundant slashes in url of resources listed in ma...
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-26 15:20 UTC by contributor
Modified: 2012-08-22 22:13 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2012-04-26 15:20:28 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html
Multipage: http://www.whatwg.org/C#offline
Complete: http://www.whatwg.org/c#offline

Comment:
How to deal with redundant slashes in url of resources listed in manifest
file? i.e. /directory///test.js was storaged in local as
http://www.example.com/directory///test.js, when user agent fetch test.js will
failed to fetch it from local since http://www.example.com/directory///test.js
was different with http://www.example.com/directory/test.js

Posted from: 182.48.107.247
User agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh_CN) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/10.0 Safari/534.7
Comment 1 contributor 2012-07-18 17:23:20 UTC 
This bug was cloned to create bug 18131 as part of operation convergence.
Comment 2 Ian 'Hixie' Hickson 2012-08-22 22:13:59 UTC 
I don't understand the question here. "http://example.com//" and "http://example.com///" are different URLs, so it makes sense to cache them differently, no?