Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Improve debug logging with ?ModPagespeedFilters=+debug or with conf file option. #191

Open
GoogleCodeExporter opened this issue Apr 6, 2015 · 15 comments

Comments

@GoogleCodeExporter
Copy link

When mod_pagespeed fetches an origin resource, the caching headers may be in 
one of several states:

1. Expiration not set
2. Expiration set in the far distant past, which might mean that the site admin 
intended to have the header be uncacheable
3. Expiration set in the past, but within the last few years, which might mean 
that the site-admin has forgotten to manually freshen the headers.
4. Expiration set in the future.


For case #3, mod_pagespeed might benefit the site admin by issuing a warning in 
the Apache error log.

Original issue reported on code.google.com by jmara...@google.com on 21 Jan 2011 at 1:58

@GoogleCodeExporter
Copy link
Author

Original comment by sligocki@google.com on 24 Feb 2011 at 10:43

  • Added labels: Type-Enhancement

@GoogleCodeExporter
Copy link
Author

Summary was: Log resources that have expired in the past when they are fetched

Original comment by jmara...@google.com on 17 Sep 2012 at 7:56

  • Changed title: Improve debug logging with ?ModPagespeedFilters=+debug or with conf file option.

@GoogleCodeExporter
Copy link
Author

Issue 489 has been merged into this issue.

Original comment by jmara...@google.com on 17 Sep 2012 at 7:56

@GoogleCodeExporter
Copy link
Author

Original comment by jmara...@google.com on 17 Sep 2012 at 7:56

  • Added labels: Milestone-v24

@GoogleCodeExporter
Copy link
Author

This issue has not yet been fully addressed, although +debug now results in 
more data about flushes.

Original comment by jmara...@google.com on 28 Nov 2012 at 7:06

  • Added labels: Milestone-v25
  • Removed labels: Milestone-v24

@GoogleCodeExporter
Copy link
Author

Original comment by jmara...@google.com on 28 Nov 2012 at 7:06

@GoogleCodeExporter
Copy link
Author

Also of interest for the 'debug' filter, indicating amount of time spent 
fetching, caching, & rewriting.

Original comment by jmara...@google.com on 30 Nov 2012 at 3:19

@GoogleCodeExporter
Copy link
Author

Issue 489 has been merged into this issue.

Original comment by jmara...@google.com on 10 Dec 2012 at 7:22

@GoogleCodeExporter
Copy link
Author

Original comment by morlov...@google.com on 14 Feb 2013 at 4:33

  • Added labels: Milestone-v26
  • Removed labels: Milestone-v25

@GoogleCodeExporter
Copy link
Author

Original comment by jkar...@google.com on 2 Apr 2013 at 2:40

  • Added labels: Milestone-v27
  • Removed labels: Milestone-v26

@GoogleCodeExporter
Copy link
Author

Original comment by matterb...@google.com on 24 Apr 2013 at 3:12

  • Added labels: Milestone-v28
  • Removed labels: Milestone-v27

@GoogleCodeExporter
Copy link
Author

Original comment by sligocki@google.com on 13 May 2013 at 8:58

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Original comment by sligocki@google.com on 24 Jun 2013 at 2:21

  • Changed state: Accepted
  • Removed labels: Milestone-v28

@GoogleCodeExporter
Copy link
Author

Is this one of the ones we just handled in the debug fixit?

Original comment by jefftk@google.com on 20 Jun 2014 at 3:21

@GoogleCodeExporter
Copy link
Author

Huh.  My CL is supposed to address this sort of thing, but I don't give
much detail about the headers when something's expired.  That'd be worth a
look, it shouldn't be that hard.

Original comment by jmaes...@google.com on 20 Jun 2014 at 8:35

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants