mod_include/3502: mod_include's mod_perl SSI hook uses wrong way to detect IncludesNOEXEC

[Todd Vierling <tv...@pobox.com>]

>Number:         3502
>Category:       mod_include
>Synopsis:       mod_include's mod_perl SSI hook uses wrong way to detect IncludesNOEXEC
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Dec  7 08:30:01 PST 1998
>Last-Modified:
>Originator:     tv@pobox.com
>Organization:
apache
>Release:        1.3.3
>Environment:
All
>Description:
In order to prevent <!--#perl sub=""--> when IncludesNOEXEC is set, handle_perl()
checks "!(ap_allow_options(r) && OPT_INCLUDES)", which is always set if
handle_perl is called.
>How-To-Repeat:
Set IncludesNOEXEC and <!--#perl sub="sub { print $$; }"--> - it mysteriously works fine.
>Fix:
Change the expression to:  (ap_allow_options(r) && OPT_INCNOEXEC)
>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!         ]