[MAGNOLIA-6914] Range support filter sets 412 (Precondition failed) Created: 05/Jan/17 Updated: 30/Sep/21 Resolved: 30/Sep/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.3.10, 5.4.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Frank Sommer | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | to-verify, y2k | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Chrome |
||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
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 |
| Comments |
| Comment by Rainer Blumenthal [ 05/Jan/17 ] |
|
This makes it impossible to host even small videos in the CMS. |
| Comment by Marta Kobus [ 30/Sep/21 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.
Thank you, The Magnolia Team |