summaryrefslogtreecommitdiffstats
path: root/docs/html/http.html
diff options
context:
space:
mode:
authorgerv%gerv.net <>2004-01-25 03:30:57 +0100
committergerv%gerv.net <>2004-01-25 03:30:57 +0100
commit6c709dd097e65025038a0dc9c17fad6a88e99b6b (patch)
treec0c33411898e67410829ea142458440fe912b388 /docs/html/http.html
parentc7f3e4a3a055bbbec29a8731f388f9fa4648c768 (diff)
downloadbugzilla-6c709dd097e65025038a0dc9c17fad6a88e99b6b.tar.gz
bugzilla-6c709dd097e65025038a0dc9c17fad6a88e99b6b.tar.xz
Massive rearrangement of the installation section. Hopefully it makes sense now.
Diffstat (limited to 'docs/html/http.html')
-rw-r--r--docs/html/http.html535
1 files changed, 0 insertions, 535 deletions
diff --git a/docs/html/http.html b/docs/html/http.html
deleted file mode 100644
index a950acce5..000000000
--- a/docs/html/http.html
+++ /dev/null
@@ -1,535 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->HTTP Server Configuration</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
-REL="HOME"
-TITLE="The Bugzilla Guide - 2.17.5
- Development Release"
-HREF="index.html"><LINK
-REL="UP"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="PREVIOUS"
-TITLE="Step-by-step Install"
-HREF="stepbystep.html"><LINK
-REL="NEXT"
-TITLE="Optional Additional Configuration"
-HREF="extraconfig.html"></HEAD
-><BODY
-CLASS="section"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->The Bugzilla Guide - 2.17.5
- Development Release</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
->Chapter 4. Installation</TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="section"
-><H1
-CLASS="section"
-><A
-NAME="http"
-></A
->4.2. HTTP Server Configuration</H1
-><P
->The Bugzilla Team recommends Apache when using Bugzilla, however, any web server
- that can be configured to run <A
-HREF="glossary.html#gloss-cgi"
-><I
-CLASS="glossterm"
->CGI</I
-></A
-> scripts
- should be able to handle Bugzilla. No matter what web server you choose, but
- especially if you choose something other than Apache, you should be sure to read
- <A
-HREF="security.html#security-access"
->Section 4.5.4</A
->.
- </P
-><P
->The plan for this section is to eventually document the specifics of how to lock
- down permissions on individual web servers.
- </P
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="http-apache"
-></A
->4.2.1. Apache <SPAN
-CLASS="productname"
->httpd</SPAN
-></H2
-><P
->You will have to make sure that Apache is properly
- configured to run the Bugzilla CGI scripts. You also need to make sure
- that the <TT
-CLASS="filename"
->.htaccess</TT
-> files created by
- <B
-CLASS="command"
->./checksetup.pl</B
-> are allowed to override Apache's normal access
- permissions or else important password information may be exposed to the
- Internet.
- </P
-><P
->You need to configure Apache to run .cgi files outside the
- <TT
-CLASS="filename"
->cgi-bin</TT
-> directory.
- Open your
- <TT
-CLASS="filename"
->httpd.conf</TT
-> file and make sure the
- following line exists and is uncommented:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;AddHandler cgi-script .cgi
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->To allow <TT
-CLASS="filename"
->.htaccess</TT
-> files to override
- permissions and .cgi files to run in the Bugzilla directory, make sure
- the following two lines are in a <TT
-CLASS="computeroutput"
->Directory</TT
->
- directive that applies to the Bugzilla directory on your system
- (either the Bugzilla directory or one of its parents).
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;Options +ExecCGI
-AllowOverride Limit
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><P
->You should modify the &#60;DirectoryIndex&#62; parameter for
- the Apache virtual host running your Bugzilla installation to
- allow <TT
-CLASS="filename"
->index.cgi</TT
-> as the index page for a
- directory, as well as the usual <TT
-CLASS="filename"
->index.html</TT
->,
- <TT
-CLASS="filename"
->index.htm</TT
->, and so forth. </P
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->For more information on Apache and its directives, see the
- glossary entry on <A
-HREF="glossary.html#gloss-apache"
-><I
-CLASS="glossterm"
->Apache</I
-></A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="http-iis"
-></A
->4.2.2. Microsoft <SPAN
-CLASS="productname"
->Internet Information Services</SPAN
-></H2
-><P
->If you need, or for some reason even want, to use Microsoft's
- <SPAN
-CLASS="productname"
->Internet Information Services</SPAN
-> or
- <SPAN
-CLASS="productname"
->Personal Web Server</SPAN
-> you should be able
- to. You will need to configure them to know how to run CGI scripts,
- however. This is described in Microsoft Knowledge Base article
- <A
-HREF="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp"
-TARGET="_top"
->Q245225</A
->
- for <SPAN
-CLASS="productname"
->Internet Information Services</SPAN
-> and
- <A
-HREF="http://support.microsoft.com/support/kb/articles/Q231/9/98.asp"
-TARGET="_top"
->Q231998</A
->
- for <SPAN
-CLASS="productname"
->Personal Web Server</SPAN
->.
- </P
-><P
->Also, and this can't be stressed enough, make sure that files such as
- <TT
-CLASS="filename"
->localconfig</TT
-> and your <TT
-CLASS="filename"
->data</TT
->
- directory are secured as described in <A
-HREF="security.html#security-access"
->Section 4.5.4</A
->.
- </P
-></DIV
-><DIV
-CLASS="section"
-><H2
-CLASS="section"
-><A
-NAME="http-aol"
-></A
->4.2.3. AOL Server</H2
-><P
->Ben FrantzDale reported success using AOL Server with Bugzilla. He
- reported his experience and what appears below is based on that.
- </P
-><P
->AOL Server will have to be configured to run
- <A
-HREF="glossary.html#gloss-cgi"
-><I
-CLASS="glossterm"
->CGI</I
-></A
-> scripts, please consult
- the documentation that came with your server for more information on
- how to do this.
- </P
-><P
->Because AOL Server doesn't support <TT
-CLASS="filename"
->.htaccess</TT
->
- files, you'll have to create a <A
-HREF="glossary.html#gloss-tcl"
-><I
-CLASS="glossterm"
->TCL</I
-></A
->
- script. You should create an <TT
-CLASS="filename"
->aolserver/modules/tcl/filter.tcl</TT
->
- file (the filename shouldn't matter) with the following contents (change
- <TT
-CLASS="computeroutput"
->/bugzilla/</TT
-> to the web-based path to
- your Bugzilla installation):
- </P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><FONT
-COLOR="#000000"
-><PRE
-CLASS="programlisting"
->&#13;ns_register_filter preauth GET /bugzilla/localconfig filter_deny
-ns_register_filter preauth GET /bugzilla/localconfig~ filter_deny
-ns_register_filter preauth GET /bugzilla/\#localconfig\# filter_deny
-ns_register_filter preauth GET /bugzilla/*.pl filter_deny
-ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny
-ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny
-ns_register_filter preauth GET /bugzilla/data/* filter_deny
-ns_register_filter preauth GET /bugzilla/template/* filter_deny
-
-proc filter_deny { why } {
- ns_log Notice "filter_deny"
- return "filter_return"
-}
- </PRE
-></FONT
-></TD
-></TR
-></TABLE
-><DIV
-CLASS="warning"
-><P
-></P
-><TABLE
-CLASS="warning"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This probably doesn't account for all possible editor backup
- files so you may wish to add some additional variations of
- <TT
-CLASS="filename"
->localconfig</TT
->. For more information, see
- <A
-HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
-TARGET="_top"
->&#13; bug 186383</A
-> or <A
-HREF="http://online.securityfocus.com/bid/6501"
-TARGET="_top"
->Bugtraq ID 6501</A
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><P
-></P
-><TABLE
-CLASS="note"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="../images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->If you are using webdot from research.att.com (the default
- configuration for the <TT
-CLASS="option"
->webdotbase</TT
-> paramater), you
- will need to allow access to <TT
-CLASS="filename"
->data/webdot/*.dot</TT
->
- for the reasearch.att.com machine.
- </P
-><P
->If you are using a local installation of <A
-HREF="http://www.graphviz.org"
-TARGET="_top"
->GraphViz</A
->, you will need to allow
- everybody to access <TT
-CLASS="filename"
->*.png</TT
->,
- <TT
-CLASS="filename"
->*.gif</TT
->, <TT
-CLASS="filename"
->*.jpg</TT
->, and
- <TT
-CLASS="filename"
->*.map</TT
-> in the
- <TT
-CLASS="filename"
->data/webdot</TT
-> directory.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="stepbystep.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="extraconfig.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Step-by-step Install</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Optional Additional Configuration</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file