It seems to be something to do with your http-server configuration. udc first calls the HEAD method on the URL given, to check the date and size against information in the cache.
It seems that your web server is returning different headers for HEAD method compared to GET. One way to see what it is returning is to use wget with --spider option, which causes wget to fetch the HEAD. wget -spider -S http://www.cs.mu.oz.au/~schroder/combined_track_bigwig.bw You can also try this online site: http://web-sniffer.net/ Here's some more interesting reading which says that the HEAD response headers should be the same as for GET, and therefore should include the content-length. http://stackoverflow.com/questions/1311892/http-head-response-set-content-length Perhaps you could ask your httpserver admins to look into it. You are the first person to report a problem like this. Please contact us again if there's anything further we can help with. -Galt > Hi, > I'm trying to view my bigWig file stored on a university server in the > UCSC browser. It's providing some fixed step data on chromosome 1 in > hg19. When loading the track, I get the following error message: > Error No Content-Length: returned in header for > http://www.cs.mu.oz.au/~schroder/combined_track_bigwig.bw > , can't proceed, sorry > Checking the header information manually, I can't find a problem with > the content length field (wget -S > http://www.cs.mu.oz.au/~schroder/combined_track_bigwig.bw > ). > Is there any error that I'm missing? > Thank you very much, > Jan Schroeder > > > Dipl.-Inf. Jan Schroeder > PhD Student > The University of Melbourne and NICTA VRL, > Victoria, Australia > > > > _______________________________________________ > Genome maillist - [email protected] > https://lists.soe.ucsc.edu/mailman/listinfo/genome _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
