Fix swob.Range docstring
Bad ranges cause a ValueError to be raised, not an empty ranges list. Change-Id: I118bd2f7dc08ff5198870f4093c6eb350506c8ed
This commit is contained in:
parent
be66aa8e76
commit
25dc7224b6
|
@ -480,8 +480,8 @@ class Range(object):
|
|||
After initialization, "range.ranges" is populated with a list
|
||||
of (start, end) tuples denoting the requested ranges.
|
||||
|
||||
If there were any syntactically-invalid byte-range-spec values,
|
||||
"range.ranges" will be an empty list, per the relevant RFC:
|
||||
If there were any syntactically-invalid byte-range-spec values, the
|
||||
constructor will raise a ValueError, per the relevant RFC:
|
||||
|
||||
"The recipient of a byte-range-set that includes one or more syntactically
|
||||
invalid byte-range-spec values MUST ignore the header field that includes
|
||||
|
|
Loading…
Reference in New Issue