#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:
----------------------------+-----------------------------------------------
Changes (by vbraun):
* cc: robertwb (added)
Comment:
I see your point about bots, though afaik that would only affect the sage
patch buildbot. I'll cc Robert, maybe he can tell us how his bot checks
freshness.
Ordinary users don't download patches from trac on a regular basis, thats
why I don't think there is any bandwidth issue. The problem with the
`~/.wgetrc` bandaid is that you often don't know whether you are behind a
transparent proxy. Sage developers regularly work away from their home
institutions / in coffee shops, and who knows what is being cached.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11813#comment:4>
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.
