#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:4 vbraun]:
 > 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.

 Robert [also] stores md5sums (or some hash code) of patches, so I assume
 he doesn't specifically use HTTP header information, and his bot ''does''
 scan the ticket's comments, in contrast to my release tool and AFAIK also
 Jeroen's. (The advantage is that you don't have to fetch and parse the --
 potentially large or long -- HTML version of a ticket at all; that's btw.
 another reason why we want the relevant files, spkgs or patches to be
 applied, to be referenced in the ticket's description.)

 [[BR]]

 > 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.

 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).

 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).

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11813#comment:5>
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.

Reply via email to