Lofesa commented on issue #2052: URL: https://github.com/apache/incubator-pagespeed-mod/issues/2052#issuecomment-732443674
Hi great Luis =;-)) Well... you have a nginx proxy+pagespeed --> apache servers (main+pagespeed, image and assets), rigth? Then Apache(main+pagespeed) get html pages that contains urls from image and assets, rigth? I think that in (nginx proxy+pagespeed) pagespeed is not needed . And you must configure Apache servers+pagespeed in each and a [downstream cache](https://www.modpagespeed.com/doc/downstream-caching). How Domain works: You have a SiteA and a SiteB. The site A generates html code that contains url from SiteB. In SiteA you have: `pagespeed Domain http*://siteA` (with this notation you cover the http and the https version) `pagespeed Domain http:*//siteB ` Whit this config, pagespeed in SiteA can rewite (aka optimize) urls from SiteB, but can´t test if the rewrited url exits in SiteB, so if SiteB don´t run pagespeed module, when a request like https://siteB/some-image.jpg.ci.pagespeed.some-hash.web comes, it returns a 404 because don´t know nothing about pagespeed rewrited url. So, when you use pagespeed Domain is only for domains you know are running pagespeed module. But you can try some like this: pagespeed Domain http*://myproyect.domain.com pagespeed MapProxyDomain https://myproyect.domain.com/images http://images.domain.com pagespeed MapProxyDomain https://myproyect.domain.com/assets http://assets.domain.com In this way all the content from http://images.domain.com are served under the url https://myproyect.domain.com/images. https://myproyect.domain.com/images this need to be a file folder to store files. ---------------------------------------------------------------- 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
