Bug 86562 - httpd-manual files installed in inconvenient location
Summary: httpd-manual files installed in inconvenient location
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: httpd
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Joe Orton
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-03-25 17:23 UTC by Robert P. J. Day
Modified: 2007-04-18 16:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-03-25 19:36:15 UTC

Attachments (Terms of Use)

Description Robert P. J. Day 2003-03-25 17:23:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
  this RPM installs all of the online HTML-format documentation
in the directory /var/www/manual.  this seems to be a bad idea,
since it's not available under the default DocumentRoot value,
so that you can't browse via the apache server itself.

  the reason this is inconvenient is that many of those files
have .en suffixes (among others), and require apache's content
negotiation to be able to follow hyperlinks.

  just browsing via a browser to file:///var/www/manual fails
pretty quickly because of this.  it would seem more reasonable
for these files to be installed under /var/www/html, or at least
for a post-install script to add a symlink to support this.

  as it is, the online HTML docs installed from this RPM
are simply not browseable.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  browse to file:///var/www/manual
2.  try to follow some of the hyperlinks
3.  note that this fails due to files ending with ".html.en", which
disagrees with the names in the hyperlinks

Expected Results:  being able to browse, of course

Additional info:

Comment 1 Joe Orton 2003-03-25 19:36:15 UTC
The default httpd.conf has:

Alias /manual "/var/www/manual"

so you can browse to http://localhost/manual/ to view the manual.

Note You need to log in before you can comment on or make changes to this bug.