Geoffroy Couprie
Geoffroy Couprie
https://twitter.com/colmmacc/status/1034492056968736768?s=19 this is a kind of load balancing where client requests can be sent to various backend servers, but each client request can have a different set of backend servers....
this log is appearing frequently, there must be a bug when closing sessions
The current trie based router is useful and reasonably fast, but is not flexible enough. Let's think about where we can go from here, what new features we want, etc....
for most HTTP calls, the request side will need a smaller buffer than the response side. Would it be interesting to allow switching to larger buffers, or using vectored IO...
if we compile a new major version of sozu (or install the package), and in the meantime, one of the worker processes panics, when the master process starts a new...
Following #588, it appears the query messages should change a bit. In previous versions, everything was organized around proxy types, then listeners. Now we get listeners from their listen address,...
default answers (404 and 503) are pregenerated, so we do not include any new headers. Would it be useful to add the request id?
right now, sozu is built to handle very large requests: it only cares about the path and the `Host` header for routing (and, in some cases, the sticky session cookie)....
currently we return a 503 when we're not able to open a TCP connection to the backend or there is no backend server available, but we simply close the session...
filter on: - HTTP method - exact path action: - redirect (with regex?) - rewrite path or domain