[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1729: Changed IP then CSS files 404
Lofesa commented on issue #1729: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-779804889 When you cleared the cache, css files are served rewrited by pagespeed or are the original css files? My bet is that some thing has changed and pagespeed is unable to fech the resources. I you try `https;//mydomain.com/?PageSpeedFilters=+debug` maybe the debug messages (as html comments in the code) have some clue. How pagespeed fecht https resources (What config have)? What domains have you authorized? Have you tried the LoadFromFile? 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
[GitHub] [incubator-pagespeed-ngx] benjaminadk commented on issue #1729: Changed IP then CSS files 404
benjaminadk commented on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-779779905
It seemed to be working for a while tonight. CSS files were all being
delivered. All I did was purge the cache a few times. Then I was switching
between Google users (chrome instances) and then all CSS 404ed again.
Could it have something to do with this session cookie?
```
#this next part requires the more_clear_headers module - if nginx fails,
remove this
if ($skip_cache = 0 ) {
more_clear_headers "Set-Cookie*";
set $rt_session "";
}
```
This is the only thing I didn't install from the previous setup. Based on
the comment I found I just skipped it.
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
