31–40 of 42 posts
Nice. It supports lua and mail alerts on changing servers now...
The mail thing seems like a not healthy growth of functionality. Most people already have logging infrastructure in place for this. Unix philosophy and all that.
Earlier quoted context omitted.
Varnish is a good HTTP caching server, but with the rise of HTTPS and soon HTTP/2 I'm not sure it'll change since last time I heard its developers don't intend to support TLS at all.
I disagree, Poul-Henning Kamp's HTTPS/HTTP2 rant is well known, but he's not going to abandon the project. He has steered it to follow the unix ideals of doing one thing well. They (varnish) forked stud and bought it up to date as hitch [1] which covers TLS. At some point they will incorporate HTTP2 once the demand is there. https://github.com/varnish/hitch
As an HAProxy user, support for logging to stdout (and hence journald) would be great. Currently HAProxy users on the major Linux distros either have to use it in debug mode or have a second log server just for the purposes of running HAProxy. Otherwise I love HAProxy!
HAProxy is not linux-specific. We have a POSIX logging facility, and HAProxy works just fine with syslog. If journald has problems with syslog, it's basically journald's problem.
If the admin wants the logs in syslog, 2>&1 | logger or similar. If the admin wants to use multilog, s6-log, or journald, that's also easy.
(For the same reasons, daemons should not include daemonization routines but should run in the foreground. If I want it in the background, I'll arrange for my process supervisor to start it.)
Earlier quoted context omitted.
Yeah, there's a mix of awesome and what? stuff. > Since 1.6, HAProxy can forge SSL certificate on the fly! Yes, you can use HAProxy with your company’s CA to inspect content. > Device Identification (Considering it seems you need a proprietary lib) > mailers > lua > Processing of HTTP request body All seem to be be moving away from what HAProxy is/was. It's not an application server. It's not a webserver. It's not a…
Lua is kinda awesome, though. Use it with plenty of common sense and it can be a very powerful tool.
Earlier quoted context omitted.
Neither seems like good functionality to add to HAProxy. They both seem superfluous and almost antithetical to what it was in 1.5. Why is it nice?
I can see some value to Lua; it allows for more complex routing rules in a way that's comfortable for a programmer. (This is pretty much what I use Lua for in nginx, too.) Mail, though--yeah, nope.
Is this possible with HAProxy? If it is, the documentation doesn't make it clear how.
Something I've always wanted to do but from what I can see is impossible in Apache is simply limit the number of connections a single IP can have open at once. Is this possible with HAProxy? If it is, the documentation doesn't make it clear how.
Haproxy btw is fantastic too, useful for hiding real location of web server from attacks
Earlier quoted context omitted.
HAProxy is not linux-specific. We have a POSIX logging facility, and HAProxy works just fine with syslog. If journald has problems with syslog, it's basically journald's problem.
In the spirit of avoiding code duplication and making daemontools-like process supervisors happy (that includes systemd for these purposes), I greatly appreciate when logs can be sent to stderr If the admin wants the logs in syslog, 2>&1 | logger or similar. If the admin wants to use multilog, s6-log, or journald, that's also easy. (For the same reasons, daemons should not include daemonization routines but should ru…
If a daemon doesn't... daemonize into the background, it's no longer a daemon - just a process.
Silly loonix folks.
Please see the FreeBSD program daemon[1] or the FreeBSD handbook section 3.8[2].
[1] https://www.freebsd.org/cgi/man.cgi?query=daemon&apropos=0&s...
[2] https://www.freebsd.org/doc/handbook/basics-processes.html
Great! But no http2 so it won't get in front of my nginx instances, yet ;)
Cool, now we can use Device Identification feature to route mobile users to a different backend, also love the HTTP/2 connection sharing.
Through our company, we have some customer who want us to integrate
into HAProxy the ability to detect device type and characteristics and
report it to the backend server. We got a couple of contributions from
2 companies experts in this domain: 51 degrees and deviceatlas. You
can now load those libraries in HAProxy in order to fully qualify a
client capabilities and set up some headers your application server
can rely on to adapt content delivered to the client or let the
varnish cache server use it to cache multiple flavor of the same
object based on client capabilities.
More on this blog later on how to integrate each product.