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

Should we add ModPagespeedRewriteUncacheableResources and/or ModPagespeedInPlaceWaitForOptimized? #661

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

Should we add ModPagespeedRewriteUncacheableResources and/or ModPagespeedInPlaceWaitForOptimized? #661

GoogleCodeExporter opened this issue Apr 6, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

Do we want to create ModPagespeedRewriteUncacheableResources?
Do we want to create ModPagespeedInPlaceWaitForOptimized?

If we want the first then we have to have the second.  The second requires docs 
and some tests to verify Apache IPRO.

Original issue reported on code.google.com by jkar...@google.com on 1 Apr 2013 at 5:50
@GoogleCodeExporter
Copy link
Author 

The log sometimes shows me proxy fetch waiting times of several seconds (about 
10-45 secs). Does this mean the content will be delivered in that time too with 
this directive activated? Wouldn't that be the opposite of the pagespeeds' 
meaning? Maybe this is onyl useful when you have a proxy server in front of 
your web server?!

Original comment by jor...@gmail.com on 11 Apr 2013 at 7:56

@GoogleCodeExporter
Copy link
Author 

InPlaceWaitForOptimized would have a timeout associated with it.  But yes, a 
good use for it would be in a proxy server.

Original comment by jkar...@google.com on 11 Apr 2013 at 10:39

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter