Received: (qmail 24018 invoked by uid 2012); 4 Dec 1997 20:50:12 -0000 Message-Id: <19971204205012.24017.qmail@hyperreal.org> Date: 4 Dec 1997 20:50:12 -0000 From: ronald klass Reply-To: ron@tencore.com To: apbugs@hyperreal.org Subject: Range header not recognized (???) X-Send-Pr-Version: 3.2 >Number: 1517 >Category: mod_headers >Synopsis: Range header not recognized (???) >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: support >Submitter-Id: apache >Arrival-Date: Thu Dec 4 14:10:00 PST 1997 >Last-Modified: Thu Dec 4 15:43:11 PST 1997 >Originator: ron@tencore.com >Organization: >Release: 1.3b3dev >Environment: TELNET to your server at www.apache.org. >Description: I cannot seem to get "Range" header to work. I am using same headers as in the example in PR#1329. Using your server www.apache.org to test, I always get the entire document. I also have same results on a version 1.2b7 server. Example: Telnet to www.apache.org port 80, then: GET / HTTP/1.1 Host: www.apache.org Range: bytes=0-100 The entire document is returned. Now my actual problem: --------------------- The same problem happens making a 1.0 request. This "hybrid" request works fine on Microsoft and Netscape servers. I'm fairly certain it worked on at least one of your Beta versions about a year ago...I'm sure I tested it (using your server). Example: GET / HTTP/1.0 Range: bytes=0-100 Again, the entire document is returned from your Apache server, version 1.3b3dev and v1.2b7. >How-To-Repeat: >Fix: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: marc State-Changed-When: Thu Dec 4 15:43:11 PST 1997 State-Changed-Why: Some documents, such as files parsed for SSIs by mod_include, can not be served in ranges. The files at http://www.apache.org/ are such files, so the entire file is returned. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]