#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 vbraun):
> 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.
Not necessarily. I often read the patch on trac (looking at the html
version), then download it with `hg qimport .../raw-attachment/x.patch`,
and then test it. Unless there are any test failures its easy to miss that
mercurial got a stale copy.
Since the upstream fix will add a `Cache-control: must-revalidate` and/or
`Vary: *`, we don't lose anything by having Apache add those headers right
now.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11813#comment:9>
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.
