Skip to content
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

throw some big warnings when HTTP servers don't implement Range headers #1132

Closed
rbuels opened this Issue Jul 21, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@rbuels
Copy link
Collaborator

rbuels commented Jul 21, 2018

To avoid confusion among people trying to put JBrowse on top of other things, particularly certain rather bare-bones python web servers.

@rbuels rbuels added this to the 1.15.1 milestone Jul 21, 2018

@cmdcolin

This comment has been minimized.

Copy link
Contributor

cmdcolin commented Jul 22, 2018

It might be better to request a specific sample file for a range request as a sanity check because, unless I am missing something, you wouldn't really know whether the http server is misbehaving until after it returns the response to download a massive file without byte-range

@cmdcolin

This comment has been minimized.

Copy link
Contributor

cmdcolin commented Jul 23, 2018

I switched to using readyState 2 from xhr and then you can get status before the file is downloaded

@rbuels rbuels added the has pullreq label Jul 23, 2018

@rbuels rbuels closed this in 9feec34 Jul 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.