Lofesa commented on issue #1897: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1897#issuecomment-970653134
I > > > For now I've added using the add_header for the cache control and it seems to show ok > > I also added a header to the location directive for static files to make sure it's processed by nginx and not by apache. > >  > > I added a similar header in apache requests to differentiate to requests processed by apache and nginx > >  > > Should I add etag off too? > > Expires directive is gone. > > Of course the 4xx error is still there. I still viewing mixed cache-control header and ioweb-served-by Only tested images, some have it, some apache and some nginx, and other don´t have the ioweb-served-by header. and 2 or 3 images returns 404. All this with pagespeed disabled ( url?PageSpeed=unplugged) All files on `https://subdomain.example.com/pub/static` comes from apache ``` 700040-babolat_all.jpg dog_dampener.jpg logo-etennis.ico ``` returns 404 More strange, image files served with ?PageSpeed=unplugged are not the same as served with ?PageSpeedFilters=+debug Whit unplugged I have these files with 404, with debug, no. Like a page cache with differen code for each url parameter. Whit unplugged I get files with etag headers from IPRO, but this no posible, pagespeed is disabled.. Image +debug  Image unplugged  Don´t have ioweb-served-by  Image served by apache, so proxy is in place and file is not under nginx location  Image served unplugged (pagespeed totally off) but have haders from IPRO (the etag header)  This make me thinking images are cached somewhere and served with the headers they have been stored. -- 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
