#11813: Stale caches with trac and transparent proxies
----------------------------+-----------------------------------------------
Reporter: vbraun | Owner: mvngu, schilly
Type: defect | Status: new
Priority: major | Milestone: sage-4.7.2
Component: website/wiki | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
----------------------------+-----------------------------------------------
Comment(by leif):
Replying to [comment:7 vbraun]:
> Replying to [comment:5 leif]:
> > But the purpose of `~/.wgetrc` in this case would be to ''always''
disable caching (by default), such that it wouldn't matter whether you're
behind a proxy or not (provided the proxy isn't broken and doesn't refuse
to bypass caching).
>
> So you are suggesting that every Sage developer puts a particular entry
in `~/.wgetrc` on all of his laptops, just to be safe if he ever leaves
his house with it.
You're right, that's of course too much to demand, compared to the minimal
effort it takes to continually install a recent version of Sage with all
necessary prerequisite patches etc. on every computer one might take with
oneself.
[[BR]]
> > Well, humans are more likely to read the comments on a ticket, so they
actually see that a patch was re-uploaded / modified (though they perhaps
don't look at the file modification times of the downloaded files, which
one IMHO should do).
>
> The html version does not get erroneously cached, the bug manifests only
with the raw attachment.
So it is safe to read the comments; I didn't say anything else. Bots
usually don't do that, which was my point.
[[BR]]
> And I don't check manually that a downloaded file has the right time
stamp, I have a computer to do menial task for me not the other way round
:-)
Well, you should notice when a patch (which you know of it was) recently
re-uploaded on trac suddenly has a modification time of months ago, and in
case you have any doubt, you can easily view the HTML version, which also
shows the ''current'' changeset header, and compare it to what you
actually downloaded or have on your disk.
[[BR]]
Hopefully this will be fixed by Edgewall, although -- despite the
discussion on sage-devel -- we still have the more than two years old
0.11.5 version.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11813#comment:8>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
