Hi, Roderick! This indicates that your server is not currently configured to support byte-ranges.
In order to use the bigDataUrl attribute of custom tracks for bigWig, bigBed, and bam files, you will need to have a server that supports byte-ranges. You may be able to request byte-range support from your admins, or find suitable alternative server. The byte-range support is used for random-access, and also for resuming downloads. Most servers today support this feature. -Galt 3/1/2011 1:34 PM, Roderick Yao: > To whom it may concern, > > I have been trying to display a bigWig file on the Genome Browser. I > entered > > *track type=bigWig name="Example" description="Test Data" bigDataUrl= > https://wodaklab.org/svn/public/bigWig_test/SRR020052.bw* > > in the "Add Custom Tracks" page, in the text box labelled "Paste URLs or > data". I got the error message > > *Byte-range request was ignored by server. Expected Partial Content 206. > https://wodaklab.org/svn/public/bigWig_test/SRR020052.bw;byterange=0-: 200 > OK Can't get data socket for > https://wodaklab.org/svn/public/bigWig_test/SRR020052.bw * > > I also tried the same thing with the bigWig example file provided on the > site and got a similar error message. When I searched the UCSC Genome > Browser mailing lists, I could not find any other instances of a similar > problem. Would you be able to tell what is causing this? > > Regards, > Roderick > _______________________________________________ > Genome maillist - [email protected] > https://lists.soe.ucsc.edu/mailman/listinfo/genome _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
