@rpedde wrote:
hrm. true. It used to fully parse the range header, but I think it got lost somewhere. :/
I’ve got it on my “things to do before next stable” list. It should be easy enough that I’ll get to it as one of the first things once the db is stable.
Glad to hear it’ll be fixed 🙂
Thanks a lot!
Thorsten