<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
On 2/3/2011 5:09 PM, Aplin, Justin M wrote:
<blockquote cite="mid:4D4B35C7.4090602@ufl.edu" type="cite">On
2/3/2011 5:53 PM, Geoff Down wrote:
<br>
<blockquote type="cite">...
<br>
Neither could I. It may be entirely in memory. Nevertheless that
was the
<br>
conclusion I came to. It's not the IP address being cached, it's
the
<br>
response from the site I would say. Your new request is never
being sent
<br>
(via your new IP) because Polipo is returning the cached version
of the
<br>
page IMO.
<br>
Anyone have other ideas?
<br>
GD
<br>
</blockquote>
<br>
Before he goes through all that trouble, wouldn't it be worth just
SOCKSifying Firefox to use Tor directly, rather than Polipo? If
it's some hidden cache issue with Polipo, the issue would
disappear then, no? Also he mentions opening a new tab, but never
says he cleared the Firefox cache; could Firefox itself simply be
fishing the page up from memory? A simple tools > clear
everything would be a decent test.
<br>
<br>
<br>
</blockquote>
I am using Torbutton. It is supposed to Torrify Firefox - yes?<br>
<br>
1) Sorry, should've mentioned clearing cache. It couldn't have been
(in this case) Firefox cache, because on one 'test,' I closed the
site's tab AND <u>cleared Fx cache</u>. Were no cookies involved.
Still same denial.<br>
<br>
2) Using Torbutton, in Preferences>Security Settings>Cache, "<u>block
Tor disk cache & clear all cache on Tor toggle</u>" is checked
by default. Implies Tor is ?? using memory cache?<br>
There is a 2nd setting, "block disk and memory cache during Tor" <br>
The Torbutton Design Documentation says Opt. 1 - above, <br>
<blockquote type="cite">This option causes Torbutton to call <a
class="ulink"
href="https://developer.mozilla.org/en/nsICacheService#evictEntries.28.29"
target="_top">nsICacheService.evictEntries(0)</a>
on Tor toggle to remove all entries from the cache. In addition,
this setting
causes Torbutton to set <a class="ulink"
href="http://kb.mozillazine.org/Browser.cache.disk.enable"
target="_top">browser.cache.disk.enable</a> to false.
</blockquote>
I confirmed Torbutton enabled does set "browser.cache.disk.enable"
to false. So when Torbutton is enabled, no cache in Fx. Therefore,
the "clear all cache on Tor toggle" must be talking about Tor mem
cache (I assume).<br>
<br>
Torbutton Preferences description (for the 2 above ):<br>
<blockquote type="cite">
<ul>
<li>Block Tor disk cache and clear all cache on Tor Toggle
<p> Since the browser cache can be leveraged to store unique
identifiers, cache must not persist across Tor sessions.
This option keeps the memory cache active during Tor usage
for performance, but blocks disk access for caching. </p>
</li>
<li>Block disk and memory cache during Tor
<p> This setting entirely blocks the cache during Tor, but
preserves it for Non-Tor usage. </p>
</li>
</ul>
</blockquote>
<br>
3) I'm sure I closed Fx, so that would've closed Torbutton &
(since mine is set to default) cleared all cache. Even though don't
have Torbutton's "Block disk & mem cache during Tor" check, when
I closed Fx & manually cleared it's cache, all disk & mem
cache should ? have been cleared. At the time, was trying to clear
every cache I could think of / find, so clicking my "Clear Cache"
addon's icon would've been 1st step.<br>
<br>
Why, after getting all new nodes & especially new exit node IP
address (I confirmed was a new address), would Tor send an <u>old
IP address</u> (? from memory) to the site? Doesn't make sense.
If Tor WAS sending an old address (to any site) after getting new
exit address, something's really wrong. Doubt that's the case.<br>
<br>
Further, for Torbutton FAQs:<br>
<blockquote type="cite"><strong><a class="anchor"
href="https://www.torproject.org/torbutton/torbutton-faq.html.en#recommendedextensions">Which
Firefox extensions do you recommend?</a></strong>
<ol>
<li><a href="https://addons.mozilla.org/firefox/addon/953">RefControl</a>
<p> Mentioned above, this extension allows more fine-grained
referrer spoofing than Torbutton currently provides. It
should break less sites than Torbutton's referrer spoofing
option.</p>
</li>
<li><a href="https://addons.mozilla.org/firefox/addon/1474">SafeCache</a>
<p> If you use Tor excessively, and rarely disable it, you
probably want to install this extension to minimize the
ability of sites to store long term identifiers in your
cache. This extension applies same origin policy to the
cache, so that elements are retrieved from the cache only if
they are fetched from a document in the same origin domain
as the cached element. </p>
</li>
</ol>
</blockquote>
Not sure about the referrer spoofing - don't think it's relevant
here. Torbutton default is to disable sending referrer header - has
nothing to do w/ an "old" IP address.<br>
SafeCache: Don't know what this Torbutton FAQ is implying. If
Torbutton disables Fx from disk caching, & if Torbutton "block
Tor disk cache..." option is checked - what's left -memory?<br>
I don't know that SafeCache does anything w/ memory cache in any
manner. So, I'm confused why Torbutton page is recommending it. Is
the <u>Torbutton</u> page assuming <u>only</u> using Tor w/o
Torbutton (which, by default, disables disk caching)?<br>
<br>
<br>
<br>
</body>
</html>