Hello, I'd live to disable HTTP persistent connections between Pound and my backend servers, but enable HTTP persistent connections between web browsers and Pound.
My thinking is: * The connections between Pound and the backend servers are unencrypted and extremely low latency, and also each web connection (on this system) requires a LOT of memory, so persistent connections here are undesirable. * The connections between web browsers and Pound is encrypted, has significant network latency, and each connection should require very little memory (whatever it takes to run a Pound thread). So persistent connections here are very desirable. I thought that simply disabling keepalive on my backend servers would be sufficient, but it seems that Pound is detecting this and then sending "Connection: close" to browsers on every request. Is my interpretation of what's going on correct? What can be done about it? Thanks! -Xan -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
