You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Peter Jakobi <ja...@informatik.tu-muenchen.de> on 1998/05/19 08:38:37 UTC

mod_include/2251: User-defined attribute names create SSI error

>Number:         2251
>Category:       mod_include
>Synopsis:       User-defined attribute names create SSI error
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon May 18 23:40:01 PDT 1998
>Last-Modified:
>Originator:     jakobi@informatik.tu-muenchen.de
>Organization:
apache
>Release:        1.2.5+
>Environment:
linux kernel 2.0 (SuSE 5.2), apache 1.2.5 binary
distribution; as well as some providers 1.2.6
>Description:
[annoying misfeature, maybe no 'hard' bug]

On 1.2.0 this worked fine (example from memory)

<!--#set var="x" value="1" comment="example" -->

On 1.2.5 and 1.2.6 Apache just returns an SSI
error to the user instead of ANY page content
(even non-ssi content is skipped)

IMHO, as with HTML user agents, also servers 
should skip attributes they don't understand
when it is necessary for the server to parse the
page. Maybe with an optional warning. That way,
the server's use of SSI statements would reflect
the browsers handling of HTML objects.
>How-To-Repeat:
see above
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]