From f35829c291277a997c45185cdfe0b701ec725374 Mon Sep 17 00:00:00 2001
From: Tim Burke <tim.burke@gmail.com>
Date: Mon, 12 Sep 2016 15:02:38 -0700
Subject: [PATCH] Bring "egregious range request" comment in line with reality

With MAX_RANGES pulled out as a constant, developers are likely to
just trust the comment rather than go verify the value.

Change-Id: I47fbd4790492b272d53ee07fe5bc87170ce2c72b
Releated-Change: I4dcedcaae6c3deada06a0223479e611094d57234
---
 swift/common/swob.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/swift/common/swob.py b/swift/common/swob.py
index 900767dbbe..d0c9338271 100644
--- a/swift/common/swob.py
+++ b/swift/common/swob.py
@@ -586,7 +586,7 @@ class Range(object):
         #
         # We're defining "egregious" here as:
         #
-        # * more than 100 requested ranges OR
+        # * more than 50 requested ranges OR
         # * more than 2 overlapping ranges OR
         # * more than 8 non-ascending-order ranges
         if len(all_ranges) > MAX_RANGES: