Re: [ANNOUNCE] haproxy-1.5.1
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 > [...] > 1.5.0 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
Re: [ANNOUNCE] haproxy-1.5.1
> 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 [...] 1.5.0 [...]
Re: [ANNOUNCE] haproxy-1.5.1
Hi Olivier, On Tue, Jun 24, 2014 at 04:04:11PM +0200, Olivier wrote: > Hello, > > > The usual URLs follow : > > Site index : http://www.haproxy.org/ > > Homepage is not updated with link to 1.5.1 (still referencing 1.5.0). 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 :-/ Regards, Willy
Re: [ANNOUNCE] haproxy-1.5.1
Hello, > The usual URLs follow : > Site index : http://www.haproxy.org/ Homepage is not updated with link to 1.5.1 (still referencing 1.5.0). Olivier
[ANNOUNCE] haproxy-1.5.1
Hi all, we've got a few bug reports since 1.5.0, among which a very annoying one reported by Finn Arne Gangstad which causes file descriptor leaks since 1.5-dev25 for clients that disappear without disconnecting. Thus I'm releasing 1.5.1 early, before everyone gets hit by this nasty bug. The usual URLs follow : Site index : http://www.haproxy.org/ Sources : http://www.haproxy.org/download/1.5/src/ Git repository : http://git.haproxy.org/git/haproxy-1.5.git/ Git Web browsing : http://git.haproxy.org/?p=haproxy-1.5.git Changelog: http://www.haproxy.org/download/1.5/src/CHANGELOG Cyril's HTML doc : http://cbonte.github.com/haproxy-dconv/configuration-1.5.html And the small change log : 2014/06/24 : 1.5.1 - BUG/MINOR: config: http-request replace-header arg typo - BUG/MINOR: ssl: rejects OCSP response without nextupdate. - BUG/MEDIUM: ssl: Fix to not serve expired OCSP responses. - BUG/MINOR: ssl: Fix OCSP resp update fails with the same certificate configured twice. - BUG/MEDIUM: Consistently use 'check' in process_chk - BUG/MAJOR: session: revert all the crappy client-side timeout changes - BUG/MINOR: logs: properly initialize and count log sockets Please continue to report anything abnormal! Best regards, Willy
