Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6914

Range support filter sets 412 (Precondition failed)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • 5.3.10, 5.4.9
    • None
    • Chrome

      Range support filter does not work correctly. I think the reason is that the created eTag is invalid. The filter creates the eTag by <file name><range-length><modification time>. With the range length the eTag differ, but the check of the If-Match header expect always the same eTag.

      1. test.mp4 --> Response Headers: Content-Range: bytes 2-4/5, ETag: test.mp4_5_1470225803166 --> 206 Partial Content
2. test.mp4 --> Request Headers: If-Match: test.mp4_5_1470225803166 --> 412 Precondition failed

        Acceptance criteria

              Unassigned Unassigned
              frank.sommer Frank Sommer
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD