Maybe this don't show in GitHub, because my response goes directly from email.
Not a good idea have a site with http/Https, Google may consider it duplicate content. Http must be redirected to Https with a 301 code. Anyway.... When you fetch the page via http, URLs in the page, get rewrites by pagespeed? El vie, 30 sept 2022 23:32, GitBox <g...@apache.org> escribió: > > bigretromike commented on issue #1755: > URL: > https://github.com/apache/incubator-pagespeed-ngx/issues/1755#issuecomment-1264042708 > > > Sorry for commig too late, but have personal issues that make me out > of internet for some time. > > > > The site runs in https, so why have you: > > > > pagespeed MapRewriteDomain "https://redacted"; "http://redacted";; > pagespeed LoadFromFile "http://redacted/wp-content/"; > "/var/www/wp-content/"; > > > > MapRewriteDomain makes any ocurrence of http://redacted is rewrited > as https://redacted, but if the site runs w/o any proxy, ssl end point or > similar thing, why you have http resources in an https page? > > > > The error you have posted say this: > > > > `# [Warning] [1502319] [image.webp:0] Resource based on > http://redacted/wp-content/uploads/2022/07/image.webp but cannot access > the original` > > > > So pagespeed is searching for a http resource. > > Thanks for replay, better than newer. > > 1. `pagespeed MapRewriteDomain "https://redacted/"; "http://redacted/";` > I added it was suggested on other forums to maybe "force" any http request > to https - with or without there is no changes looks like I leave those > uncommented. > 2. `pagespeed LoadFromFile "http://redacted/wp-content/"; > "/var/www/wp-content/";` even if the page serve content thru https, the > fallback to http made it tricky as it is same server for http/https content > but I would prefer all traffic go thry https so I mapped http url location > to local path, also another thing that I tested with and without, and this > one cut a lot of errors. still did not resolve issue with https page > getting called back by pagespeed thru http. > 3. Yes, page does run without proxy, the page runs fine on http also > but it is servered via https without any content pointing to http (aka no > mixed content) > 4. both https and http for > `redacted/wp-content/uploads/2022/07/image.webp` is available. > > > -- > 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 > >
