[users@httpd] cache control header missing on HEAD request for cache miss

2020-12-05 Thread rakesh r
Cache control header missing for HEAD request but works for GET.


curl -I https://localhost/support.html  -k
HTTP/1.1 200 OK
Date: Thu, 19 Nov 2020 16:35:48 GMT
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: frame-ancestors 'self'
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Type: text/html;charset=utf-8
Content-Language: en

Using GET

curl -i http://localhost/support.html
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: frame-ancestors 'self'
Last-Modified: Thu, 19 Nov 2020 18:57:55 GMT
Accept-Ranges: bytes
Content-Length: 206001
Expires: Fri, 20 Nov 2020 18:58:00 GMT
Vary: Accept-Encoding
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Cache-Control: public, max-age=86400
Content-Type: text/html
Content-Language: en


Rule Used :


Header set Cache-Control "public, max-age=86400"


this behavior happens when content is not cached on Apache request is
passed to the backend server and on the response header is missing .
when the content is cached on apache header is inserted properly.

Thanks

Rakesh


Re: [users@httpd] slotmem error still occuring after updating to Apache 2.4.43 APR 1.7.0

2020-12-05 Thread Yann Ylavic
On Fri, Dec 4, 2020 at 7:45 PM Wendell Hatcher
 wrote:
>
> This has nothing to do with underlying SHM stuff and everything to do with 
> how multiple balancers, global and outside of virtual hosts, are initialized 
> and sometimes persisted. This was changed greatly in 2.4.29.You should find 
> the minimal set of balancers that reproduces the error and It is likely 
> related to duplicate virtual hosts or duplicate proxy "workers".

Could you please provide the full error_log (with LogLevel debug) of
the httpd startup failure?
If there are multiple instances (and potential duplicates), the
error_log of all the instances may help too (with LogLevel debug,
still).

Regards;
Yann.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org