Add setting to cap number of activity days to display

This patch adds a setting, 'web.activityDurationMaximum', that specifies the
maximum number of days of activity that may be requested. The default value is
30. When the number of days requested exceeds this value, the request is
handled as though the maximum value was requested.

1 files changed, 4 insertions, 0 deletions

diff --git a/src/main/java/com/gitblit/wicket/pages/BasePage.java b/src/main/java/com/gitblit/wicket/pages/BasePage.java
index c9e11b08..2bab1183 100644
--- a/src/main/java/com/gitblit/wicket/pages/BasePage.java
+++ b/src/main/java/com/gitblit/wicket/pages/BasePage.java
@@ -325,6 +325,7 @@ public abstract class BasePage extends SessionPage {
 		String regex = WicketUtils.getRegEx(params);

 		String team = WicketUtils.getTeam(params);

 		int daysBack = params.getInt("db", 0);

+		int maxDaysBack = GitBlit.getInteger(Keys.web.activityDurationMaximum, 30);

 

 		List<ProjectModel> availableModels = getProjectModels();

 		Set<ProjectModel> models = new HashSet<ProjectModel>();

@@ -372,6 +373,9 @@ public abstract class BasePage extends SessionPage {
 

 		// time-filter the list

 		if (daysBack > 0) {

+			if (maxDaysBack > 0 && daysBack > maxDaysBack) {

+				daysBack = maxDaysBack;

+			}

 			Calendar cal = Calendar.getInstance();

 			cal.set(Calendar.HOUR_OF_DAY, 0);

 			cal.set(Calendar.MINUTE, 0);