is_cacheable() was set to return false for blame or blame_incremental
which both use unique urls so there's no reason this shouldn't pass
through the caching engine.
Leaving the function in place for now should something actually arrise
that we can't use caching for (think ajaxy kinda things likely).
Signed-off-by: John 'Warthog9' Hawley <warthog9@xxxxxxxxxxxxxx>
---
gitweb/gitweb.perl | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 5eb0309..1d8bc74 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -798,7 +798,8 @@ our %actions = (
);
sub is_cacheable {
my $action = shift;
- return !($action eq 'blame_data' || $action eq 'blame_incremental');
+ # There are no known actions that do no involve a unique URL that shouldn't be cached.
+ return 1;
}
# finally, we have the hash of allowed extra_options for the commands that
--
1.7.2.3
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html