Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
bugzilla
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
etersoft
bugzilla
Commits
18dc27ad
Commit
18dc27ad
authored
Nov 21, 2001
by
barnboy%trilobyte.net
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added bit about needing proper <Directory> permissions in order
for .htaccess to function. See bug 97668.
parent
845248d9
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
64 additions
and
2 deletions
+64
-2
installation.sgml
docs/sgml/installation.sgml
+32
-1
installation.xml
docs/xml/installation.xml
+32
-1
No files found.
docs/sgml/installation.sgml
View file @
18dc27ad
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook
V4.1
//EN"> -->
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook
XML V4.1.2
//EN"> -->
<chapter id="installation" xreflabel="Bugzilla Installation">
<title>Installation</title>
...
...
@@ -1203,6 +1203,37 @@ bash# ./checksetup.pl
</note>
</para>
<para>
The default .htaccess file may not provide adequate access
restrictions, depending on your web server configuration.
Be sure to check the <Directory> entries for your
Bugzilla directory so that the <filename>.htaccess</filename>
file is allowed to override web server defaults. For instance,
let's assume your installation of Bugzilla is installed to
<filename>/usr/local/bugzilla</filename>. You should have
this <Directory> entry in your <filename>httpd.conf</filename>
file:
</para>
<para>
<programlisting>
<![CDATA[
<Directory /usr/local/bugzilla/>
Options +FollowSymLinks +Indexes +Includes +ExecCGI
AllowOverride All
</Directory>
]]>
</programlisting>
</para>
<para>
The important part above is <quote>AllowOverride All</quote>.
Without that, the <filename>.htaccess</filename> file created by
<filename>checksetup.pl</filename> will not have sufficient
permissions to protect your Bugzilla installation.
</para>
<para>
If you are using Internet Information Server or other web
server which does not observe <filename>.htaccess</filename>
...
...
docs/xml/installation.xml
View file @
18dc27ad
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook
V4.1
//EN"> -->
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook
XML V4.1.2
//EN"> -->
<chapter
id=
"installation"
xreflabel=
"Bugzilla Installation"
>
<title>
Installation
</title>
...
...
@@ -1203,6 +1203,37 @@ bash# ./checksetup.pl
</note>
</para>
<para>
The default .htaccess file may not provide adequate access
restrictions, depending on your web server configuration.
Be sure to check the
<
Directory
>
entries for your
Bugzilla directory so that the
<filename>
.htaccess
</filename>
file is allowed to override web server defaults. For instance,
let's assume your installation of Bugzilla is installed to
<filename>
/usr/local/bugzilla
</filename>
. You should have
this
<
Directory
>
entry in your
<filename>
httpd.conf
</filename>
file:
</para>
<para>
<programlisting>
<![CDATA[
<Directory /usr/local/bugzilla/>
Options +FollowSymLinks +Indexes +Includes +ExecCGI
AllowOverride All
</Directory>
]]>
</programlisting>
</para>
<para>
The important part above is
<quote>
AllowOverride All
</quote>
.
Without that, the
<filename>
.htaccess
</filename>
file created by
<filename>
checksetup.pl
</filename>
will not have sufficient
permissions to protect your Bugzilla installation.
</para>
<para>
If you are using Internet Information Server or other web
server which does not observe
<filename>
.htaccess
</filename>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment