mod_include/4426: Mod_include is using a string literal where it shoudn't.

[Dylan Griffiths <Dy...@Bigfoot.com>]

>Number:         4426
>Category:       mod_include
>Synopsis:       Mod_include is using a string literal where it shoudn't.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Sun May 16 23:30:00 PDT 1999
>Last-Modified:
>Originator:     Dylan_G@Bigfoot.com
>Organization:
apache
>Release:        1.3.6
>Environment:
Linux 2.2.9 w/ GCC 2.7.2
>Description:
I was frustrated because I could not get SSI to produce an output.  The solution?
<!--#echo ...
Worked fine.  However, my HTML files mostly used
<!-- #echo
Which worked with Xitami (PERLSSI) because it would parse through each comment field for the hash and a valid SSI command.
mod_include does not do that.  Instead, it looks for the string literal <!--#

>How-To-Repeat:
Just add any number of white spaces between !-- and the hash.
>Fix:
This should be changed so that any number of spaces (spaces only) may be present between !-- and #
>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. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]