Received: (qmail 60219 invoked by uid 501); 23 Feb 2001 17:26:41 -0000 Message-Id: <20010223172641.60218.qmail@apache.org> Date: 23 Feb 2001 17:26:41 -0000 From: Simon Flood Reply-To: S.M.Flood@ucs.cam.ac.uk To: submit@bugz.apache.org Subject: /~user/ doesn't work X-Send-Pr-Version: 3.110 >Number: 7303 >Category: mod_userdir >Synopsis: /~user/ doesn't work >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: apache >Arrival-Date: Fri Feb 23 09:30:01 PST 2001 >Closed-Date: Fri Apr 06 07:56:43 PDT 2001 >Last-Modified: Fri Apr 06 07:56:43 PDT 2001 >Originator: S.M.Flood@ucs.cam.ac.uk >Release: 1.3.17 >Organization: >Environment: Novell NetWare 5.1 with Support Pack 2a applied. Apache installed from pre-compiled binary available from www.apache.org >Description: Have installed Apache on to server from pre-compiled binary. All I have changed in HTTPD.CONF are the following: * ThreadsPerChild 5 (from 50) * Uncommented lines to use status.nlm and info.nlm modules * ExtendedStatus On * Port 81 (server is also running NetWare Enterprise Server on port 80) * ServerAdmin * ServerName Everything else is as supplied. My server is the single server in O=Testing in it's own tree. Apart from objects created during installation of NetWare 5.1 I have only created three additional users called (imaginatively!) user1, user2, and user3. I have created a USER (traditional rather than NSS, using DOS and LONG name space) on which I have created three directories - user1, user2, and user3. Using NetWare Administrator I have assigned each user a home directory (so this is stored in NDS) and granted each user RWCEMF rights to their directory. Within user's home directory I have created a sub-directory public_html and created both an index.html and index.htm file with minimal content. When I try and access http:///~user1 or variations (/~user1/, /~user1.testing/, etc.) it produces a 404 error. I have tried giving server object RF rights to user's home directory and setting O=Testing as the bindery context. >How-To-Repeat: Set up NetWare 5.1 using default settings and install Apache. After installation change settings as detailed above. >Fix: No I'm afraid that I'm not much of a C++ programmer but I have looked at the source for mod_userdir.c and compared it with a version of the file found at http://poli.cs.vsb.cz/novell/apache (posted in response to an earlier reported bug in mod_userdir) and I can see that there are differences. I've tried downloading and using the provided ApacheC.nlm but it doesn't work with the latest Apache.nlm provided with version 1.3.17. Does Apache pick up the user's home directory from NDS (rather than rely on a particular path)? Many thanks, Simon >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: bnicholes State-Changed-When: Fri Apr 6 07:56:43 PDT 2001 State-Changed-Why: MOD_USERDIR supports the same user home directory functionality as on all other platform. This does not include NDS based user home directories. Although Novell has released a module called MOD_HDIRS that does support NDS based user home directories. This module can be downloaded from the Novell DeveloperNet site at: http://developer.novell.com/ndk/modapach.htm Class-Changed-From-To: sw-bug-change-request Class-Changed-By: bnicholes Class-Changed-When: Fri Apr 6 07:56:43 PDT 2001 >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]