Lofesa commented on issue #1749: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1749#issuecomment-1169883226
@danidorado > I had this directive set up inside the http block at nginx.conf file > pagespeed LoadFromFileCacheTtlMs 31536000000; That's ok. I mentioned this because I don't see it in the config you posted. Only one apreciation, maybe 1 year is too much time. That's supposed to be the time pagespeed stores the optimized resource in their cache . Forgot the LoadFromFile stuff.... for a momment. If you serve a resource with 1 week as cache-control header and is optimized by pagespeed, 2 things go on: 1.- The cache-control for the optimized resource is changed to 1 year (unless you configured pagespeed to preserver the original header) 3.- The original cache-control, 1 week in the example, is taken by pagespeed as the time the resource lives in their cache. > if i'm not wrong having that TTL set then I could skip doing this part you mentioned, right? > Or any other custom header (those added to request with the nginx add_header), with >pagespeed AddResourceHeader Ummm... Not. That only affect cache-control. If you whish to add a custom header to the resource ( say strict-transport as example) this must be added with `pagespeed AddResourceHeader`. As far as the resource is loaded from disk and don't have any http headers, when the optimized resource is serverd it only have the default headers pagespeed put in the optimized resource, and strict-transport is not in these defaults, and don't have it even you set an add_header nginx directive. >pagespeed SslCertDirectory directory; >pagespeed SslCertFile file; You are rigth, don't need these directives as far as the request for an optimized resource not file based goes by http, not https. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pagespeed.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
