Traffic Server
  1. Traffic Server
  2. TS-1265

Bad range requests still yields 206 responses

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.4
    • Component/s: HTTP
    • Labels:
      None

      Description

      If you send a request like e.g.

      Range: byte=90000-

      (note byte and not bytes), it should really give a 406 response code, but it seems to give a 206 instead, with a 1 byte length response body (Content-Length: 1).

        Activity

        Leif Hedstrom created issue -
        Alan M. Carroll made changes -
        Field Original Value New Value
        Assignee Alan M. Carroll [ amc ]
        Hide
        Alan M. Carroll added a comment -

        Commit b57523bdbb1e45a88d2e4ee78ba4f1649a116039

        Updated logic for checking validity of ranges.

        Show
        Alan M. Carroll added a comment - Commit b57523bdbb1e45a88d2e4ee78ba4f1649a116039 Updated logic for checking validity of ranges.
        Alan M. Carroll made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Leif Hedstrom made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        23h 43m 1 Alan M. Carroll 22/May/12 00:11
        Resolved Resolved Closed Closed
        15d 50m 1 Leif Hedstrom 06/Jun/12 01:01

          People

          • Assignee:
            Alan M. Carroll
            Reporter:
            Leif Hedstrom
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development