These directives near the ModPagespeedSslCertDirectory
"/opt/bitnami/common/openssl/certs"
line.
ModPagespeedFetchHttps enable
ModPagespeedSslCertFile file
ModPagespeedDomain http*://*.knoozi.com
file is a cert.pem file that is in the ".../openssl/cert/" directory.
W/o these directives, the https config is not complete.
As an improvement, to bypass the https fecht of resources, you can configure
LoadFromFile, this make pagespeed load files directly from disk w/o fechting
with a https request.
ModPagespeedLoadFromFile "https://www.knoozi.com"; "/var/www/example/"
ModPagespeedLoadFromFileRuleMatch Disallow *
ModPagespeedLoadFromFileRuleMatch allow
\.(js|css|jpg|jpeg|png|pdf|gif)(\?.*)?$
Whit these directives you mean:
1.- All static resources in your domain can be read from disk in that directory
2.- All files from these directory are forbiden
3.- Only files w/ these extensions are loaded.
For /var/www/example/ you must set your root directory for www.knoozi.com
domain, That is to say the same directory where wp-config.php is.
Try all these directives and test if it work. I can´t test the site now because
pagespeed is disabled.
P.D. Sorry for the late response.
P.D bis: Pagespeed don´t work well with url or filenames with non ascii (or a
subset of utf8) characters.
[ Full content available at:
https://github.com/apache/incubator-pagespeed-mod/issues/1801 ]
This message was relayed via gitbox.apache.org for [email protected]
