Lofesa commented on issue #1986: Uncacheable content, preventing rewriting of... URL: https://github.com/apache/incubator-pagespeed-mod/issues/1986#issuecomment-605604866 Not bother at all. These directives are wrong: ``` ModPagespeedSslCertDirectory /etc/letsencrypt/live/domain.com ModPagespeedSslCertFile cert.pem ``` The certificates you need here are NOT the let´s encrypt certifivates you are using in your site. Thing in a browser, when you take a look at the certificates you can see a lot of "upper" level certificates, these are from the CA sites. Rigth? These CA certificates are needed for validate the let´s encrypt cert that you use in your site. Rigth? Well, pagespeed module uses a headless browser (called Serf, you can see this word in your logs as a User agent text) so these browser need to have CA certificates to validate the let`s encrypt. I can see you use both directives, so I may think you use a redhat-centos linux distro, so the rigth directives are: ``` ModPagespeedSslCertDirectory /etc/pki/tls/certs ModPagespeedSslCertFile /etc/pki/tls/cert.pem ``` If the site respond to https request you don´t need to rewrite the domain. For SEO purposes you need some apache rewrite rules to redirect http to https, some like: ``` RewriteEngine On RewriteCond %{HTTPS} !=on RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R=301,L] ``` In this way your site only do https request
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
