httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark J Cox <>
Subject Content-type "image/gif;qs=0.5" breaks browsers.
Date Thu, 18 Jul 1996 07:25:33 GMT
Will sending a Content-type of "image/gif;qs=0.5" break older browsers?

The HTTP/1.0 spec says that sending a Content-type with attached
parameters is legal but "Some older HTTP applications do not recognize
media type parameters. HTTP/1.0 applications should only use media type
parameters when they are necessary"

HTTP/1.1 draft says "When sending data to older HTTP applications,
implementations should only use media type parameters when they are
required by that type/subtype definition. "

A quick straw poll revealed:

	Ignored parameters
		Any version of Netscape on Unix/PC
		Compuserve Browser/Spry Mosaic 4

		Microsoft Internet Explorer [PC, even version 3.0b1!]
		NSCA Mosiac 2.0 [PC] ("Undefined mime type")
		Netmanage Webserver 5 ("Unknown file type")

Should we strip any parameters from the content-type before we return
it to the browser?


Escape character is '^]'.
HEAD /icons/image HTTP/1.0
Accept: */*

HTTP/1.0 200 OK
Date: Thu, 18 Jul 1996 07:45:06 GMT
Server: Apache/1.1.0
Content-Type: image/jpeg;qs=0.9
Set-Cookie: Apache=www1334837675925273; path=/
Last-Modified: Thu, 18 Jul 1996 07:44:34 GMT
ETag: "2f58-621-31edeb62"
Accept-Ranges: bytes
Content-Length: 1569
Vary: Accept


View raw message