#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 [ticket:11813 vbraun]:
 >   4. Download the patch again - under some circumstances the old version
 of the patch is served by the (not so) transparent proxy.
 > [[BR]]
 > This just happened to me with `trac11115-cached_cython.patch`.

 Well, if you name it such...

 SCNR

 [[BR]]

 > A workaround is to set the `Pragma: no-cache` in the client query (i.e.
 use `wget --no-cache`), but then its easy to forget that.

 You can put it into `~/.wgetrc`.

 [[BR]]

 > Irrespective of who is precisely at fault, we should configure the trac
 server to never allow caching of the patches since their integrity is
 crucial for us and client-side caching doesn't really buy us much. For
 that, I propose to configure Apache to add the following to the headers
 for all resources under `/sage_trac/raw_attachment`:
 {{{
 Cache-Control: no-cache
 Expires: Thu, 1 Jan 1970 00:00:00 GMT
 }}}
 > hitting both the HTTP/1.0 and 1.1 cache control mechanisms.

 Hmmm, I cannot tell how large the impact ''on the machine running trac''
 will be, but in general I think that's a bad idea.

 I don't think it will be large at the moment ''for ordinary users'', as
 most patches are [hopefully] small, but note that this also inhibits the
 use of `-N` (`--timestamping`), which is more [or also] crucial to the
 ''client side'', especially for bots (or if you have a very slow, or
 expensive / volume-taxed connection).

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