Our Systems group has indicated that the server that I'd been using does not always serve byte-range requests successfully, and pointed me to a different server. Using this alternative server, I just loaded the seven bigWig custom tracks to mm9 and am able to browse them again.
I apologize for flagging this issue to you. It seems to have been a problem are our end. Gordon On 2011-09-06, at 4:30 PM, Gordon Robertson wrote: Until last week, I could load bigWig files into the mm9 browser, using a file containing a set of 7 custom track lines. This had given no problems for months. Each line was of this form (the example uses a dummy path and filename) - track type=bigWig name=myName description="..." color=50,50,150 maxHeightPixels=40:40:20 db=mm9 alwaysZero=on visibility=full bigDataUrl=http://myPath/my.bigwig Today, though I can load BED and WIG files, when I try to submit the bigWig custom track file I get the following error for each track line - Error Byte-range request was ignored by server. Expected Partial Content 206. http://mypath/my.bigwig;byterange=0-: 200 OK Can't get data socket for http://myPath/my.bigwig If I paste http://mypath/my.bigwig into a browser URL field, I'm offered the bigwig file as a download -- so the file seems to be available. We have a local mirror here, which we think was updated on the weekend, and it gives the same error message. Could you help us to understand or resolve this issue? Thanks in advance for your help. Gordon -- Gordon Robertson BC Cancer Agency Genome Sciences Centre Vancouver BC Canada www.bcgsc.ca<http://www.bcgsc.ca/> -- Gordon Robertson BC Cancer Agency Genome Sciences Centre Vancouver BC Canada www.bcgsc.ca<http://www.bcgsc.ca> _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
