Received: (qmail 37933 invoked by uid 501); 9 Oct 2000 00:59:07 -0000 Message-Id: <20001009005907.37932.qmail@locus.apache.org> Date: 9 Oct 2000 00:59:07 -0000 From: William Rowe Reply-To: wrowe@apache.org To: submit@bugz.apache.org Subject: SSI generates garbage in 2.0 alpha 7 X-Send-Pr-Version: 3.110 >Number: 6641 >Category: mod_include >Synopsis: SSI generates garbage in 2.0 alpha 7 >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sun Oct 08 18:00:00 PDT 2000 >Closed-Date: Wed Oct 18 15:25:23 PDT 2000 >Last-Modified: Wed Oct 18 15:25:23 PDT 2000 >Originator: wrowe@apache.org >Release: 2.0a7 >Organization: >Environment: applies to all >Description: SSI generates garbage in 2.0 alpha 7... some text is displayed but it's all mangled. Yes, I know this is being discussed on new-httpd, but wanted to let others know it is an issue under 2.0a7 if you have downloaded it. >How-To-Repeat: Create an SSI page with SSI directives and try to load it from the browser. >Fix: No, but I understand rbb is fast at work on this, and it should be working under 2.0a8 when that is released. >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: rbb State-Changed-When: Wed Oct 18 15:25:22 PDT 2000 State-Changed-Why: Mod_include works again. This will be available in the next Apache 2.0 alpha or beta. >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]