>Number:         5365
>Category:       os-windows
>Synopsis:       shtml Files not parsed correctly or execution of <!--#exec> 
>command not working in Apache 1.3.9 Win32
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Nov 25 06:10:00 PST 1999
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.9
>Environment:
Windows 98 SE
Apache 1.3.9
>Description:
I was running Apache 1.3.6 under Windows 98 SE and everything was working just
fine, after upgrading to 1.3.9 however (the newest Apache release for Win32) it 
did not display SHTML files correctly anymore. 

The configuration was exactly the same and the environment did not change at 
all. Apache seemed to have problems executing the program in the #EXEC tag ... 
the browser output was a white window ... or a timeout ... in rare cases it did 
work after long minutes of waiting, but it did not seem to have a pattern...

I uninstalled 1.3.9 and installed 1.3.6 again and it worked correctly once 
again without any troubles ... again, the configuration (httpd.conf) was not 
changed and the environment the same as well ...

Does anyone else have this problem?
>How-To-Repeat:

>Fix:
Perhaps it is the way Apache executes the programs now in an own child 
process...
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <[EMAIL PROTECTED]> 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!     ]