phpgroupware-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-tracker] [Bug #3110] phpGroupware Documentation conflicts


From: nobody
Subject: [Phpgroupware-tracker] [Bug #3110] phpGroupware Documentation conflicts with Apache Documentation
Date: Fri, 04 Apr 2003 19:33:01 -0500

=================== BUG #3110: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3110&group_id=509

Changes by: Dave Hall <address@hidden>
Date: Sat 04/05/2003 at 10:33 (Australia/Melbourne)

            What     | Removed                   | Added
---------------------------------------------------------------------------
            Category | None                      | API - Documentation
          Resolution | None                      | Invalid
         Assigned to | None                      | skwashd
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
This is not a phpgw bug, but a misconfiguration of apache.

If phpgw is installed in the document root, then the /doc config option should 
be disabled, especially to the world.  IMHO it is poor security to have server 
docs available anywhere except on a secure LAN.  Even then the need for it is 
questionable, most docs can be read locally using lynx or some other text based 
browser on the server - the sysadmin is the only person who requires such docs 
- and they should have ssh access to the box.

If phpgw is running on a virtual host then the /doc directory should not 
available, especially to the world.



=================== BUG #3110: FULL BUG SNAPSHOT ===================


Submitted by: meebey                  Project: phpGroupWare                 
Submitted on: Fri 04/04/2003 at 18:32
Category:  API - Documentation        Bug Group:  0.9.14.002 release        
Severity:  5 - Major                  Priority:  Low                        
Resolution:  Invalid                  Assigned to:  skwashd                 
Status:  Closed                       Component Version:  BZIP2             
Platform Version:  Linux - Debian     Reproducibility:  Every Time          

Summary:  phpGroupware Documentation conflicts with Apache Documentation

Original Submission:  I installed groupware to the root of htdocs because I use 
subdomains for groupware... (groupware.domain.xx)
In groupware are links to the groupware documentation which is in the groupware 
installation. That documentation is placed under /doc of phpgroupware root, 
that directory name conflicts with the default Apache documentation which is 
also /doc, the Apache /doc alias has higher priority than the groupware /doc 
directory, so I can't access the documentation of phpgroupware.
The name of the documentation directory should be changed in groupware to avoid 
name conflicts with apache...

Follow-up Comments
*******************

-------------------------------------------------------
Date: Sat 04/05/2003 at 10:33       By: skwashd
This is not a phpgw bug, but a misconfiguration of apache.

If phpgw is installed in the document root, then the /doc config option should 
be disabled, especially to the world.  IMHO it is poor security to have server 
docs available anywhere except on a secure LAN.  Even then the need for it is 
questionable, most docs can be read locally using lynx or some other text based 
browser on the server - the sysadmin is the only person who requires such docs 
- and they should have ssh access to the box.

If phpgw is running on a virtual host then the /doc directory should not 
available, especially to the world.

-------------------------------------------------------
Date: Sat 04/05/2003 at 00:17       By: cw
if you're going to install an app to the the root of apache you need to make 
sure everything else in that root is gone.  phpgroupware by default is designed 
to install to it's own dir, if you need to change that then you will have to do 
whatever it takes to make apache happy with it.


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3110&group_id=509




reply via email to

[Prev in Thread] Current Thread [Next in Thread]