On Tue, Jun 24, 2014 at 04:19:20PM +0200, Olivier wrote: > > I don't understand, you're the third one to tell me that, while I have > > updated it 5 minutes after the announce. One of my coworkers had the > > same issue while I had it display the updated version, and he saw it > > correctly after a forced reload, indicating that the old copy was > > cached in his browser. But I find it surprizing that so many people > > have a browser doing excessive caching :-/ > > i'm sure this is not browser caching, I made sure of this before > disturbing you with an email ;) > > GET / HTTP/1.1 > Host: www.haproxy.org > [...] > HTTP/1.1 200 OK > Date: Tue, 24 Jun 2014 14:16:32 GMT > Server: Apache (Unix; Formilux/0.1.8) > Last-Modified: Tue, 24 Jun 2014 10:52:28 GMT > Accept-Ranges: bytes > Cache-Control: max-age=28800 > Expires: Tue, 24 Jun 2014 22:16:32 GMT > Vary: Accept-Encoding > Content-Type: text/html > Content-Encoding: gzip > X-Cache: MISS from www.haproxy.org > Transfer-Encoding: chunked > [...] > <td><a href="/download/1.5/src/haproxy-1.5.0.tar.gz">1.5.0</a></td>
Ah OK, we were not speaking about the same thing, due to the previous report of my coworker. In your case these are just the links, and yes I forgot to update them :-) Done now! Thanks for the explanation ! Willy
