start and endcoordinate requests sometimes return too much data.

[viklund]

Running with the starter-kit-storage-and-interfaces demo docker compose we can find start and end coordinate combinations that return too much from the files endpoint (the same is also true in the s3 endpoint). This is using the s3 backend storage.

In the first example below, we get the correct number of bytes and in the second we get too many, even though start coordinate only increased by 10. And then increasing startCoordinate by another 10 it returns correct number of bytes again. It is not that it returns a lot when too big range is requested, it more seems to be where in the file the request is made.

$ token=$(curl -s -k https://localhost:8080/tokens | jq -r '.[0]')
$ curl -H "Authorization: Bearer $token" -k 'http://localhost:8443/files/EGAF74900000001?startCoordinate=60&endCoordinate=110' | wc -c
50
$ curl -H "Authorization: Bearer $token" -k 'http://localhost:8443/files/EGAF74900000001?startCoordinate=60&endCoordinate=120' | wc -c
32768
$ curl -H "Authorization: Bearer $token" -k 'http://localhost:8443/files/EGAF74900000001?startCoordinate=70&endCoordinate=120' | wc -c
50