> Will sending a Content-type of "image/gif;qs=0.5" break older browsers?
>
> HTTP/1.1 draft says "implementations should only use media type parameters
> when they are required by that type/subtype definition. "
Heres a patch that strips all mime type paramaters unless someone _really_
wants to send them. I can't think of any situations that need the
subtype definition so I'll submit this on Monday if I see no objections.
Mark
*** http_protocol.c Wed Jul 17 09:29:35 1996
--- http_protocol.c.new Fri Jul 19 10:35:05 1996
***************
*** 660,670 ****
char *nuke_mime_parms (pool *p, char *content_type)
{
! /* How marvelous. Arena doesn't *accept* "text/html; level=3"
! * as a MIME type, so we have to strip off the parms.
*/
! #ifndef ARENA_BUG_WORKAROUND
return content_type;
#else
--- 660,671 ----
char *nuke_mime_parms (pool *p, char *content_type)
{
! /* How marvelous. Arena and many other browsers don't *accept*
! * "text/html; level=3" as a MIME type, so we have to strip off the parms.
! * Lets remove them all unless someone really wants them
*/
! #ifdef DONT_NUKE_MIME_PARMS
return content_type;
#else
|