You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Klaus Johannes Rusch <Kl...@atmedia.net> on 1997/03/20 14:40:01 UTC
config/241: HTTP media parameters cannot be defined with Apache configuration
>Number: 241
>Category: config
>Synopsis: HTTP media parameters cannot be defined with Apache configuration
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: apache (Apache HTTP Project)
>State: open
>Class: change-request
>Submitter-Id: apache
>Arrival-Date: Thu Mar 20 05:40:01 1997
>Originator: KlausRusch@atmedia.net
>Organization:
apache
>Release: 1.1.1
>Environment:
-
>Description:
The HTTP specs provide for parameters for the Content-Type header:
media-type = type "/" subtype *( ";" parameter )
e.g.
text/html; charset=ISO8859-2
With Apache, only the first blank delimited token is accepted in the AddType directive,
any additional paramters are ignored (actually taken as - rather unlikely - extensions).
Omitting the blank before the parameters breaks some existing browsers.
None of the workarounds - asis documents and Action handlers - is nice as some of the
server's functionality is lost when serving documents that way (such as, SSI, If-Modified-Since).
>How-To-Repeat:
AddType text/html; charset=ISO8859-2 html
>Fix:
As it is very unlikely people have configured extensions like charset=ISO8859-2, a change to
interpret anything with an equals sign as parameter would improve the functionality while
at the same time maintain compatibility pretty well.
%0
>Audit-Trail:
>Unformatted: