Hosting IGV files for the web app, Fail Status: 0

[Ian Brabb]

Hello all,

Currently I'm working with running the IGV web app and finding ways to host data so that is accessible by collaborators. so far, while every file we've uploaded from a local drive has been able to load and display correctly, every file we host from our universities public server where we store the file gives us the following error:

For genome upload:

Error accessing resource: https://public.vetmed.wsu.edu/DuttkeLab/plants2023/genomes/TAIR10_Ensemble_genome.fa.fai Status: 0

for bed.gz upload:

Error accessing resource: https://public.vetmed.wsu.edu/DuttkeLab/plants2023/Athaliana_csRNA/beds/A.thaliana-cells_csRNA-seq_r1.bed.gz Status: 0: https://public.vetmed.wsu.edu/DuttkeLab/plants2023/Athaliana_csRNA/beds/A.thaliana-cells_csRNA-seq_r1.bed.gz

the same errors were given for two other species fastas and fasta indexes. all files we've attempted to upload as well from local or to the current version of the downloadable IGV app work just fine and display the data properly.

Lastly, My IT group tried another topics suggestion of an extension for "CORS javascript", but we also came to the same "Status: 0" error.

Any help would be much appreciated!

[igv-help]

Hi, I'm not able to access those files, perhaps they are behind a firewall?  If you are able to place files on a public server I will investigate further, however the most likely cause of this error is missing CORS headers in the responses.   The easiest way to investigate this is with Chrome development tools, or equivalent in another browser.   You then can examine the http requests and server responses from the "network" tab.   Below is an example from our own igv web app, igv.org/app.   The refseq gene resource "ncbiRefSeq.tx.gz" url is selected.  Notice the Headers for the request, particularly the Response Headers "Access-Control-Allow-Headers" and "Access-Control-Allow-Origin" headers.   These must be present.    

[Ian Brabb]

Hello All,

I gave this information to my IT group for the server and they were able to get the correct headers added.

Thank you much for the help!