[tor-bugs] #16326 [Tor Browser]: Verify cache isolation for Request and Fetch APIs

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Jul 10 04:23:25 UTC 2015


#16326: Verify cache isolation for Request and Fetch APIs
-----------------------------+----------------------
     Reporter:  mikeperry    |      Owner:  tbb-team
         Type:  defect       |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  Tor Browser  |    Version:
   Resolution:               |   Keywords:  ff45-esr
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+----------------------

Comment (by arthuredelstein):

 Replying to [comment:5 arthuredelstein]:
 > The Fetch API is off by default until Firefox 39. We can turn it on for
 testing by setting "dom.enabled.fetch" to true in FF 38. Weirdly, I can't
 get `fetch(...)` to cache the responses it receives, even if I include the
 option `{cache: "force-cache"}`.

 Even more weird... the response apparently is cached. I wrote a simple
 example:
 https://arthuredelstein.github.io/tordemos/fetch-caching.html

 I=On the network panel of the developer console, I can see a 304 (not
 modified) response on the second load after clearing the cache. However,
 the `fetch`ed file does not appear in about:cache anywhere. So there's
 something odd going on.

 I'm going to postpone further work on this until ff45-esr.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16326#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list