Current time: 01-19-2021, 04:14 AM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Site vs File (Browser Caching) Different? Why?
10-09-2013, 02:41 AM
Post: #9
RE: Site vs File (Browser Caching) Different? Why?
(10-08-2013 07:43 PM)robzilla Wrote:  Yeah, the age is now 593784 so apparently these files aren't purged properly.

As for your images within 3p_content showing no cache headers (on stat.*), that's probably a problem in your nginx configuration.

Quote:However, I am still confused why it does show on the CURL but WPT still says there is no max-age.

Since it's a CDN, you may be hitting a different edge server locally than WPT is from its test location.

Hey robzilla,

I got it all figured out. Thanks! I individually invalidated the files that were listed on the WPT page and the 3p_content; There was a previous directive in the NGINX config that was overriding the config I showed you. All fixed now :-)

Thanks again,
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: Site vs File (Browser Caching) Different? Why? - qops1981 - 10-09-2013 02:41 AM

Forum Jump:

User(s) browsing this thread: 1 Guest(s)