Hi, When running Varnish in front of RGW+Civetweb you want to pipe [0] request from Varnish to Civetweb.
Varnish will act as a simple TCP Proxy and sends a "Connecton: close" header to the backend. Civetweb doesn't seem to honor this query, so it doesn't send back a "Connection: close" header in the response. This causes a client to retry the request to Varnish, but it gets back ad "Broken Pipe" since Varnish already closed the connection to Civetweb. Any ideas on how we can turn this behavior of Civetweb off? With Varnish in front I actually don't want Civetweb to do KeepAlive. Varnish talks keepalive with my clients, but not between Varnish and Civetweb. It's Civetweb which doesn't honor the "Connection: close" header properly, but that might be harder to fixed. I opened a new issue [1] where we should make it configurable if HTTP KeepAlive is enabled for Civetweb or not. Wido [0]: https://www.varnish-software.com/blog/using-pipe-varnish [1]: http://tracker.ceph.com/issues/12110 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
