
This is consistent with what we already do for other semantically-invalid values like "bytes=--1". Previously, we would return a 416 Requested Range Not Satisfiable response like we do for the semantically-valid-but-not-really-meaningful "bytes=-0" Change-Id: I932b42406c9a5ee7eaa6978a655e61022a957415