general/3010: ErrorDocument 401/403 dies with SIGSEGV

[Petr Hubeny <ps...@capitol.cz>]

>Number:         3010
>Category:       general
>Synopsis:       ErrorDocument 401/403 dies with SIGSEGV
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Sep 16 08:40:00 PDT 1998
>Last-Modified:
>Originator:     psh@capitol.cz
>Organization:
apache
>Release:        1.3.1
>Environment:
Linux rt 2.0.34-p1 #14 Wed Aug 19 16:36:38 CEST 1998 i586 unknown
gcc 2.7.2.1

>Description:
I tried to use ErrorDocument for handling 401/403 codes, but client says
'Document contains no data' and server error log states:
[Wed Sep 16 17:15:15 1998] [error] client 194.212.67.1:6184 denied by server configuration: /home/psh/public_ht
ml/forbidden/index.html
[Wed Sep 16 17:15:16 1998] [notice] httpd: child pid 9731 exit signal Segmentation fault (11)

>How-To-Repeat:
I've following in my srm.conf:
Alias /errordoc/ /var/web/errordocuments/
ErrorDocument 401 /errordoc/401
ErrorDocument 403 /errordoc/403
ErrorDocument 404 /errordoc/404

And in access.conf I have:
<Directory /var/web/errordocuments>
Options MultiViews IncludesNOEXEC FollowSymLinks
AllowOverride None

order allow,deny
allow from all
</Directory>

Troubles I do create by having two subdirectories in my public_html, called
private and forbidden, with respective .htaccess files:

private/.htaccess:
AuthType Basic
AuthName "PsH's Playground"
require valid user
AuthUserFile /home/psh/public_html/private/.passwd

forbidden/.htaccess:
order deny,allow
deny from all


What puzzles me, the ErrorDocument 404 works fine.
>Fix:

>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!         ]