Opened 15 years ago
Closed 15 years ago
#5909 closed defect (fixed)
UPNP Sends 416 invalid response for satisfiable ranges.
| Reported by: | Owned by: | dblain | |
|---|---|---|---|
| Priority: | major | Milestone: | unknown |
| Component: | upnp | Version: | unknown |
| Severity: | medium | Keywords: | easy |
| Cc: | Ticket locked: | no |
Description
The attached patch will return partial content for ranges that are too long. Currently myth returns 416 for such ranges which causes the PS3 upnp client to hang when attempting to fast forward.
According to rfc2616: If a syntactically valid byte-range-set includes at least one byte- range-spec whose first-byte-pos is less than the current length of the entity-body, or at least one suffix-byte-range-spec with a non- zero suffix-length, then the byte-range-set is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server SHOULD return a response with a status of 416 (Requested range not satisfiable). Otherwise, the server SHOULD return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body.
Patch to adjust ranges that are too long.