Closed Bug 277260 Opened 20 years ago Closed 18 years ago

Requested Range Not Satisfiable error when getting to site:

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED INCOMPLETE

People

(Reporter: bz, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 I sometimes get three errors when trying to get to sites (www.pinetreeproductions.com is just an example). First go to site: "Requested Range Not Satisfiable None of the range-specifier values in the Range request-header field overlap the current extent of the selected resource. Apache/2.0.44 (Unix) DAV/2 PHP/4.3.4 mod_jk2/2.0.2 Server at www.pinetreeproductions.com Port 80" Refresh works fine, but if I try to go back to homepage I get it again. Not a lot, but have seen it on other sites. JMA Reproducible: Sometimes Steps to Reproduce: 1. 2. 3.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20050106 Firefox/1.0+ I could get to the page you specified this time. The error message corresponds to code 416, and the question is why you were sedning a range specifier in the first place. See http://www.httpsniffer.com/http/100417.htm
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Though there is no recipe for reproduction, this looks like a True Bill on the face of it, at least to the extent that there may be some error handling or reporting to fix.
Assignee: bross2 → nobody
Are you still able to reproduce this? If so, we should probably move it to Core::Networking.
I'm going to close this as INCOMPLETE. If you're able to reproduce with Firefox 2.0.0.3 or later using a new profile and can give some steps to reproduce, please comment and reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.