>Number: 4719 >Category: general >Synopsis: symbolic linked index.html not recognized as DirectoryIndex >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sat Jul 10 01:20:00 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.2.x and 1.3.x >Environment: This is occurring on both Solaris 2.5.1 and Linux 2.2.4 and 2.2.5 >Description: I received notification that a user was able to browse my server's directories. Stripping the filename off the URL I too was presented with a directory list. The list included index.html. Checking the system I confirmed that index.html was indeed a symbolic link back to another directory's index.html (this directory was created by a web-based script and linked rather than copied index.html)
DirectoryIndex is set to index.html and FollowSymLinks is activated. Replacing the linked file with a static file solved the problem instantly. Symbolic links are definitely working as all the CGI scripts in the directory are linked back to the same directory as the original index.html. >How-To-Repeat: Create one directory with index.html, create another directory with index.html linked back to the original. View through browser. >Fix: It would seem that a test is occurring that does not acknowledge index.html as a legitimate file. Simple fix - honor the sym-linked index.html. >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! ]