NGINX byte-range support is not configurable about ansible-galaxy-extras

[abretaud]

👍 the jbrowse tool needs this too

[pcm32]

My question would be then, the optional proxy_force_ranges on should go here https://github.com/galaxyproject/ansible-galaxy-extras/blob/master/templates/nginx.conf.j2#L126 ?

or somewhere else?

[mvdbeek]

Hmm, that doesn't sound completely right. The primary target for byte-range requests is the datasets controller, and this doesn't need the the proxy_force_ranges flag on our setup, which uses ansible-galaxy-extras to configure nginx. Do you have a specific route / test command that is failing ?
Alternatively here's a command to verify it works without this flag:

curl -H "range: bytes=0-8" https://usegalaxy.org/datasets/bbd44e69cb8906b5feba48dc6b55f34f/display

usegalaxy.org isn't using this flag either as far as I can tell: https://github.com/galaxyproject/usegalaxy-playbook/blob/master/env/main/templates/nginx/usegalaxy.j2

[pcm32]

Yes, requests would be inside the /datasets/<uuid>/ as you suggest.