Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Date: 25 Jun 2003 20:34:54 -0000
Message-ID: <20030625203454.28966.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 21095] New:  -
    SSI error

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21095>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21095

SSI error

           Summary: SSI error
           Product: Apache httpd-2.0
           Version: 2.0.46
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_include
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: kevinmvarley@yahoo.com


We're experiencing a problem with SSIs in both Apache 2.0.44 and 2.0.46.  I 
have posted this issue to the apache users group twice to see if anyone else 
has run into this same problem but I never heard any response.  I also 
searched through bugzilla for any bugs that might be similar.

Initially, we noticed that, on certain pages on our site, SSI directives would 
stop being processed about halfway through the page.  I began looking into the 
problem by checking our syntax, looking for any wierd characters in a hex 
editor and then finally by making small changes to the file to see if it 
affected the service of the page.  The first oddity that I came across was 
that if I opened up the problematic file and inserted a single space at the 
beginning, the SSI directives would all be correctly processed.  If I again 
removed the space, the problem came back..about halfway down the page, after a 
block of SSI conditionals, the rest of the SSIs were not processed and the SSI 
tags were sent to the browser.  After a little more investigation, I noticed 
that the problem seemed to always manifest itself when the last character of 
an SSI conditional block (e.g.  the final > in <!--#endif-->) occurred at the 
8000th byte in the file .  To test this out, I created a completely new test 
file, ensuring that the final character in a conditional SSI block was the 
8000th byte and I placed another include immediately after the conditional 
block.  Sure enough, the directives in the conditional block were processed 
successfully but the include after the conditionals was sent to the browser.  
I then tested this same issue out using a virtual include directive instead of 
a conditional block and the result was the same.

I tried my hand with the mod_include source and added some debug statements 
but, honestly, I'm not much of a C coder and I'm not terribly familliar with 
the internals of Apache.

I have attached two versions of my test file, one that works 
(test_working.html) and one that doesnt (test_broken.html).  The only 
difference between these two files is a space at the very beginning.

Additional platform and version information is listed at the bottom of this 
description.  Please let me know if you need any additional information.  
Thanks.

Kevin

OS: Debian Linux 3.0, 2.4.18 kernel
Platform: Intel x86
Apache version: 2.0.44, 2.0.46

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org