Closed
Bug 54959
Opened 25 years ago
Closed 25 years ago
images in <a href> won't load using HTTP/1.1
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
People
(Reporter: bteague, Assigned: gagan)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20000930
BuildID: 2000093006
Images that are also links are not displayed on any page on this server if the
HTTP version in Preferences...>Debugging>Networking is set to 1.1. The server
connection appears to time out. Changing it to 1.0 resolves the issue.
Reproducible: Always
Steps to Reproduce:
load the following URL:
http://www.ruf.rice.edu/~themob/
Actual Results: Connection times out.
Expected Results: Load the image!
I've seen this problem all over the web. Ars Technica, especially,
(http://www.arstechnica.com) exhibits the problem.
the following simplified test case reproduces the bug.
<html>
<a href="mob.html"><img border="0"
src="http://www.ruf.rice.edu/~themob/logo_99.jpg" width="408" height="546"></a>
</html>
|
||
Comment 2•25 years ago
|
||
All images are loaded with linux buil 100214.
|
||
Comment 3•25 years ago
|
||
confirmed with 102708 mozilla trunk build on RedHat6.2 With HTTP/1.0 set the
image appears, with HTTP/1.1 set the image flashes very briefly and disappears.
I see the same problem on the branch build today 10/27 bug cannot enable
HTTP1.0 because the pref pane is gone. Setting bug status to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
Reporter | |
Comment 4•25 years ago
|
||
yay! it's finally got someone's attention!
you can set the network HTTP version by adding a line to your prefs.js file:
user_pref("network.http.version", "1.0");
or you can change "1.0" to "1.1" for the newer version.
|
||
Comment 5•25 years ago
|
||
Confirming also on linux Netscape 6.0 release build. The problem seems to be
that the server is not specifying a HTTP version number in the response.
According to the spec this means that the recipient (in this case, mozilla)
must assume the simple HTTP/0.9 format, which is exactly what we do.
However, the response is not in simple HTTP/0.9 format. It is still in
HTTP/1.0 format. This therefore explains why when you click on the link
to the image, you see HTTP headers displayed preceeding the JPEG data.
The following demonstrates the servers response to a 1.1 GET.
GET /~themob/logo_99.jpg HTTP/1.1
host: www.ruf.rice.edu
HTTP 200 Document follows
Date: Tue, 21 Nov 2000 02:09:36 GMT
Server: NCSA/1.5.1
Last-modified: Sun, 07 May 2000 00:52:14 GMT
Content-type: image/jpeg
Content-length: 62009
There are two approaches to solving this problem. The first, is to simply
downgrade to always using HTTP/1.0 (via prefs.js), but clearly that is far
from optimal. Ideally, we should provide a server capabilities entry for
NCSA/1.5.1. This will allow us to flag this situation and fallback on HTTP
1.0 instead of HTTP 0.9.
|
|
||
Comment 7•25 years ago
|
||
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•