New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add note about Range support #7323
Conversation
Add note explaining that nginx sendfile support is required for Range (and thus IGV/JBrowse) to work.
the special `X-Accel-Redirect` header. Dataset security is maintained in this configuration because nginx will still | ||
check with Galaxy to ensure that the requesting user has permission to access the dataset before sending it. | ||
Nginx can assume this task instead and as an added benefit, speed up downloads. In addition, both the IGV genome browser and JBrowse tool (run within Galaxy) require support for the HTTP *Range* header, and this is only available if nginx (or Apache | ||
with sendfile support) serves datasets. This is accomplished through the use ofthe special `X-Accel-Redirect` header. Dataset security is maintained in this configuration because nginx will still check with Galaxy to ensure that the requesting user has permission to access the dataset before sending it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd duplicate the added text in doc/source/admin/apache.md
instead of mentioning (or Apache with sendfile support)
.
the special `X-Accel-Redirect` header. Dataset security is maintained in this configuration because nginx will still | ||
check with Galaxy to ensure that the requesting user has permission to access the dataset before sending it. | ||
Nginx can assume this task instead and as an added benefit, speed up downloads. In addition, both the IGV genome browser and JBrowse tool (run within Galaxy) require support for the HTTP *Range* header, and this is only available if nginx (or Apache | ||
with sendfile support) serves datasets. This is accomplished through the use ofthe special `X-Accel-Redirect` header. Dataset security is maintained in this configuration because nginx will still check with Galaxy to ensure that the requesting user has permission to access the dataset before sending it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with sendfile support) serves datasets. This is accomplished through the use ofthe special `X-Accel-Redirect` header. Dataset security is maintained in this configuration because nginx will still check with Galaxy to ensure that the requesting user has permission to access the dataset before sending it. | |
with sendfile support) serves datasets. This is accomplished through the use of the special `X-Accel-Redirect` header. Dataset security is maintained in this configuration because nginx will still check with Galaxy to ensure that the requesting user has permission to access the dataset before sending it. |
@nsoranzo Want to open a quick followup with those extra changes, or would you like for me to? +1 to both (looks like I merged this ~40 seconds before your review comments showed up! :)) |
Add note explaining that nginx sendfile support is required for Range (and thus IGV/JBrowse) to work.