[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1686: Random 404s on re-written images (nginx with shared Redis cache)

[GitBox <gi...@apache.org>]

Lofesa commented on issue #1686:
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-621450890


   > The redirects.inc are just for some old urls to 301 them to new pages, they don't do anything with pagespeed.
   I´m not talkin about pagespeed but about you site. In the config you have posted the server is listening in ports 80 and 443 then w/o any redirect from port 80 to the 443 you have 2 identical sites, 1 for http and 1 for https. Google can penalize with duplicate contents.
   > I'm not sure about the +debug, I've disabled image re-writing on production because of this and cannot just re-enable it to test. What i can tell you though is that for a few weeks all was fine, then new images were added to the site and they got rendered as 404s.
   
   The +debug is a url parameter you can set in the url:
   https://yourdomain.com/?PageSpeedFilters=+debug
   This paremeter inject debug messages in the html code, you can view it viewing the source code from the page.
   > 
   > At the same time I noticed that the redis DB was 99.9999% full (potentially un-realted, although there was 1GB of space in it to be used).
   > 
   Maybe the problem is the redis db size. Can you try to increase it?
   The pagespeed cache need to be larger than all the resources optimized cause it need to store several image versions for example.
   The redis at 99% is a spected behaviour cause pagespeed don´t have a clean process for it and then the clean process is the allkeys-lru from redis.
   
   If pagespeed can´t optimize a resource then it remember this fail for a time, I don´t remember if this time is a fixed amount or configurable.
   
   


----------------------------------------------------------------
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:
users@infra.apache.org