5 ms·
I'm reading over Matt's work carefully, but my initial inclination is not to merge the bulk of this into stud mainline. I'd rather keep stud simple and protoco
by jamwt 15y ago
I'm reading over Matt's work carefully, but my initial inclination is not to merge the bulk of this into stud mainline. I'd rather keep stud simple and protocol-naive and have HAProxy do the HTTP work.
- jamwt 15y agoWhich is to say indirectly that I think the right answer is for nginx (and daemons generally) to support the PROXY protocol, or some other agreed-upon standard for a naive upstream proxy to indicate host/port information.
- stock_toaster 15y agoI really agree with this. I think keeping stud as simple as possible is a great goal.
- sciurus 15y agoCould someone link to a description of the PROXY protocol?
- stock_toaster 15y agohttp://haproxy.1wt.eu/download/1.5/doc/proxy-protocol.txt http://haproxy.1wt.eu/download/1.5/doc/proxy-protocol.txt
- seiji 15y agoI'm reading over Matt's work carefully Thanks for the consideration! initial inclination is not to merge the bulk of this into stud mainline I agree. The HTTP stuff is still too integrated. ifdefs are ugly. The solution is to do what showed up when I was 99% done working on XFF -- the nice PROXY protocol addition. We just need to get PROXY support into nginx now to obviate my XFF machinations.