[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #KOO-280301]: Reading data via URLs in IDV: setting Content-Length and Accept-Ranges headers

> apache apparently does not enable "accept range" by default. also see
> http://www.unidata.ucar.edu/software/netcdf-java/reference/HTTPservice.html

Thanks John. Sorry for the confusion Dave.

I'm still a bit unclear on some of this. It seems a bit strange as I'm seeing 
"Accept-Range: bytes" headers in responses from the unidata web server but 
can't access a netCDF file from the server (even though I can access that file 
on disk). I was assuming that if the "Accept-Range: bytes" header is returned 
then byte ranges were supported.

I'm seeing the HEAD request with a 200 response in the logs (and when I do that 
I get the "Accept-Range: bytes" header). However, I'm not seeing a byte range 
request following those HEAD requests in the logs. Instead I'm seeing OPeNDAP 
.dds requests (which fail). Why isn't ToolsUI making byte range request? Does 
it depend on whether "Content-Length" or "Transfer-Encoding: chunked" is 
returned as well?

Below are the headers I get in LiveHTTPHeaders.




GET /software/netcdf-java/testdata/20010721.nc HTTP/1.1
Host: www.unidata.ucar.edu
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: 
Gecko/20080404 Firefox/
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
 UCARCA=2.0; __utma=197911339.2074733571.1188921896.1213026127.1213111663.56; 
__utmb=53293036; __utmc=53293036; 

HTTP/1.x 200 OK
Date: Tue, 10 Jun 2008 19:08:56 GMT
Server: Apache
Last-Modified: Fri, 09 May 2003 07:39:10 GMT
Etag: "a561f-185380-3bd3653168380"
Accept-Ranges: bytes
Content-Length: 1594240
Keep-Alive: timeout=15, max=2000
Connection: Keep-Alive
Content-Type: application/x-netcdf

Ticket Details
Ticket ID: KOO-280301
Department: Support THREDDS
Priority: Normal
Status: Open

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.