pagespeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1681: Uncacheable content, preventing rewriting of image
Date Tue, 03 Mar 2020 10:31:28 GMT
Lofesa commented on issue #1681: Uncacheable content, preventing rewriting of image
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1681#issuecomment-593879105
 
 
   Hi
   The s-maxage is a transient header. The resource is not optimized yet, so must not be stored
in any intermediate cache for more than 10 sec.
   I have trouble debuging your site, when I put https://www.weedstreet420.com/?PageSpeedFilters=+debug
(note the + sign) the site enter in an infinite loop.
   
   Can you try to set 
   `ModPagespeedSupportNoScriptEnabled false`
   
   In other hand, all the images are served with a `cache-control: nostore, nocache` . I don´t
know if these header is set by your origin server or by clodflare.... can you instruct cloudflare
to respect origin headers?
   In developer mode clodflare is set to DYNAMIC, this mode don´t send the assets stored
in their cache but do all the magic with header and other optimizations you set in cloudflare.
The better way to eliminate cloudflare in the debug path is putting all in grey in the dns
section. In this way, cloudflare do nothing and the request are served directly from the origin
webserver.
   As you can see in the image no filters are enabled, and no debug messages are set in the
html cod, only the bottom stuff. When I try to enable any filter in the url, get and infinite
loop, s can´t test it.
   (To enable a filter with the url https://www.weedstreet420.com/?PageSpeedFilters=+rewrite_images
. The + sign enables it and the - sign disables)
   
   ![tempsnip](https://user-images.githubusercontent.com/22342793/75766822-06b56f80-5d42-11ea-84b8-ce984819be9e.jpg)
   

----------------------------------------------------------------
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


With regards,
Apache Git Services

Mime
View raw message