Fix wrongly generated Content-Range header for PATCH /api/v4/jobs/:id/trace request
What does this MR do?
Fixes wrongly generated Content-Range header for PATCH /api/v4/jobs/:id/trace request.
Why was this MR needed?
Please look into #3275 (closed) for context.
Are there points in the code the reviewer needs to double check?
Does this MR meet the acceptance criteria?
- Documentation created/updated
- Tests
- Added for this feature/bug
- All builds are passing
- Branch has no merge conflicts with
master(if you do - rebase it please)
What are the relevant issue numbers?
Closes #3275 (closed)
Edited by Kamil Trzciński