#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 robertwb):
Replying to [comment:2 leif]:
> Replying to [ticket:11813 vbraun]:
> > 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).
This is the correct solution--it's what you do when you have a URI whose
content may change. I don't think it'll be a severe issue for developers
to hit trac itself rather than transparent proxies and it's a worthy price
to pay for always getting the correct version. The raw patch is certainly
cheaper on the server and connection than the html version.
Currently, there's only one patchbot and it's running locally, so no
transparent proxy that I'm aware of :). In general, it only downloads
patches when a new one was added (it parses the main ticket page (rss
feed)). Patches are identified with md5 hashes, so although it could get
confused by caches if they were in the way, when it gets a new version of
a patch it doesn't get confused.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11813#comment:12>
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.
