Lofesa edited a comment on issue #1995: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1995#issuecomment-639631972
Fecht from pagespeed can´t reach the origin resource. No matter if you can do it via curl or a browser. To fecht an https resource, pagespeed need to have ModPagespeedFetchHttps enabled, but this need to be done with the apropiate certificates, same as a browser need the CA certificates to evaluate the web server certificates. This is acomplised by enabling ModPagespeedSslCertDirectory directory and ModPagespeedSslCertFile file as stated in the [doc](https://www.modpagespeed.com/doc/https_support#configuring_ssl_certificates) Read the doc and take account the differences between a RedHat/Centos and Ubuntu/Debian distros. The request that have the message `<!--The preceding resource was not rewritten because its domain (www.limelight.consulting) is not authorized--><!--The preceding resource was not rewritten because its domain (www.somewebsite.com) is not authorized-->` can´t throw a 404 error but it can´t be optimized by pagespeed. In these message you have posted 2 domains: www.limelight.consulting and www.somewebsite.com. Are both domans running pagespeed? I assuem that ww.somewebsite.com is your own domain where pagespeed is running and the other mentioned domain not. So you need a ModPagespeedDomain http*://*.somewebsite.com ---------------------------------------------------------------- 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
