Eric, On 8/4/21 13:18, Eric Covener wrote:
On Wed, Aug 4, 2021 at 12:59 PM Christopher Schultz <chris@xxxxxxxxxxxxxxxxxxxxxx> wrote:Reic, On 8/4/21 11:17, Eric Covener wrote:On Wed, Aug 4, 2021 at 11:08 AM Christopher Schultz <chris@xxxxxxxxxxxxxxxxxxxxxx> wrote:All, Can httpd automatically set Keep-Alive response header based upon the KeepAlive and other configuration settings? Something like this: HTTP/1.1 200 OK Server: Apache/2 Date: Wed, 04 Aug 2021 15:00:00 GMT Content-Length: 12345 Connection: keep-alive Keep-Alive: timeout=5; max=100I'm interested in httpd generating that last response-header for me.httpd does generate this by default, matching your settings. You will even see the "max" tick down.Hmm. I'm not seeing that. I'm using httpd 2.4.48 as provided by Amazon Linux's yum repository. $ wget -SO /dev/null https://my.site/ HTTP/1.1 200 200 Cache-Control: no-cache, no-store, must-revalidate Content-Type: text/html;charset=UTF-8 Date: Wed, 04 Aug 2021 16:57:00 GMT Expires: 0 Permissions-Policy: interest-cohort=() Pragma: no-cache Server: Apache/2 Strict-Transport-Security: max-age=15552000 X-Content-Type-Options: nosniff Content-Length: 10799 Connection: keep-alive I will note that it's going through Amazon's Elastic Load balancer, so perhaps the header is being stripped.This is probably it. The Keep-Alive header is hop-by-hop since if you have a proxy between you and the server, the "connection" being kept alive isn't really the one you have access to.
Ack. I'll see if there's anything ELB does/doesn't do about this kind of thing. I know for sure that keep-alives are supported because we are using them for our pipelined API requests.
Thanks, -chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|