Received: (qmail 69768 invoked by uid 501); 15 May 2000 12:13:39 -0000
Message-Id: <20000515121339.69759.qmail@locus.apache.org>
Date: 15 May 2000 12:13:39 -0000
From: Michael McLagan <Michael.McLagan@Linux.Org>
Reply-To: Michael.McLagan@Linux.Org
To: submit@bugz.apache.org
Subject: [Sun May 14 23:35:04 2000] [error] [client 198.182.196.10] premature EOF in parsed file /home/linuxorg/html/footer.html
X-Send-Pr-Version: 3.110

>Number:         6086
>Category:       mod_include
>Synopsis:       [Sun May 14 23:35:04 2000] [error] [client 198.182.196.10] premature EOF in parsed file /home/linuxorg/html/footer.html
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon May 15 05:20:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Michael.McLagan@Linux.Org
>Release:        1.3.12
>Organization:
apache
>Environment:
Linux 2.2.15, Redhat 6.2, self compiled
>Description:
The encoding apptribute requires quotes around the "none".  The documentation
is not clear on this point.  Putting a document out without the quotes is 
disasterous -- it terminates parsing, with prejudice, leaving out the remainder
of the parsed file.  In our case that left the site showing blank pages to 
Netscape clients for a significant amount of time.  

FWIW, I think making the default "entity": when the previous default was "none" 
was an extremely poor choice.  1.3.12 broke a significant amount of our site
and required much work to upgrade as a result of this additional "feature" 
which changed the default behavior.
>How-To-Repeat:
<!--#echo encoding=none var="REMOTE_SERVER" -->
>Fix:
Graceful error handling would be appropriate -- why abort the file instead 
finding the matching --> and continuing on with the rest of the include?  A 
meaningful and comprehendible error message would make a good second choice.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> 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!     ]