W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2011

[whatwg] AppCache-related e-mails

From: Michael Nordman <michaeln@google.com>
Date: Tue, 2 Aug 2011 16:44:57 -0700
Message-ID: <CAHpoE=iFosBjKbf+8UymmAXc-pxEgfHfBntheX3P+umdui6O0Q@mail.gmail.com>
On Tue, Aug 2, 2011 at 4:40 PM, Ian Hickson <ian at hixie.ch> wrote:

> On Tue, 2 Aug 2011, Michael Nordman wrote:
> > >>
> > >> A common request that maybe we can agree upon is the ability to list
> the
> > >> manifests that are cached and to delete them via script. Something
> > >> like...
> > >>   String[] window.applicationCache.getManifests();  // returns
> appcache
> > >> manifest for the origin
> > >>   void window.applicationCache.deleteManifest(manifestUrl);
> > >
> > > This is trivial to do already; just return 404s for all the manifests
> > > you no longer want to keep around.
> >
> > It involves creating hidden iframes loaded with pages that refer to the
> > manifests to be deleted, straightforward but gunky.
>
> If you actively want to seek out old manifests, sure, but what's the use
> case for doing that? It would be like trying to actively evict things from
> HTTP caches.
>
>
> > >> 0. [DONE] A means of not invoking the fallback resource for some error
> > >> responses that would generally result in the fallback resource being
> > >> returned. An additional response header would suite they're needs...
> > >> something like...
> > >> x-chromium-appcache-fallback-override: disallow-fallback
> > >> If a response header is present with that value, the fallback response
> > >> would not be returned.
> > >> http://code.google.com/p/chromium/issues/detail?id=82066
> > >
> > > What's the use case? When would you ever want to show the user an
> > > error yet really desire to indicate that it's an error and not a 200
> > > OK response?
> >
> > Google Docs. Instead of seeing a fallback page that erroneously says
> > "You must be offline and this document is not available.", they wanted
> > to show the actual error page generated by the server in the case of a
> > deleted document or when the user doesn't have rights to access that
> > doc.
>
> I don't see what's wrong with using 200 OK for that case.
>

You should talk to the app developers. I think there are other consumers of
these urls besides the browser. To change the status code to 200 would break
those other consumers.


>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>
Received on Tuesday, 2 August 2011 16:44:57 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:35 UTC