summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorjake%bugzilla.org <>2008-04-04 13:46:41 +0200
committerjake%bugzilla.org <>2008-04-04 13:46:41 +0200
commita522277200d67fce50cf686910abc397a3368ebf (patch)
tree2b5aed38cf156b4420e7ed13f59d4e11ffe97f05 /docs
parent9ccb15f6f063c269cd85f74998d466cbc7d5d35d (diff)
downloadbugzilla-a522277200d67fce50cf686910abc397a3368ebf.tar.gz
bugzilla-a522277200d67fce50cf686910abc397a3368ebf.tar.xz
Refix bug 201955 - Forgot to edit one of the introductory paragraphs and fixed a couple other minor errors.
Diffstat (limited to 'docs')
-rw-r--r--docs/en/xml/installation.xml18
1 files changed, 8 insertions, 10 deletions
diff --git a/docs/en/xml/installation.xml b/docs/en/xml/installation.xml
index 02dff197c..d128c4798 100644
--- a/docs/en/xml/installation.xml
+++ b/docs/en/xml/installation.xml
@@ -1,5 +1,5 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
-<!-- $Id: installation.xml,v 1.50 2008/04/04 06:46:40 jake%bugzilla.org Exp $ -->
+<!-- $Id: installation.xml,v 1.51 2008/04/04 06:46:41 jake%bugzilla.org Exp $ -->
<chapter id="installation">
<title>Installation</title>
@@ -1065,8 +1065,7 @@ man 5 crontab
</section>
- <section id="content-type"
- xreflabel="Preventing untrusted Bugzilla content from executing malicious Javascript code">
+ <section id="content-type">
<title>Preventing untrusted Bugzilla content from executing malicious
Javascript code</title>
@@ -1077,16 +1076,15 @@ man 5 crontab
requirements mentioned in
<ulink
url="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"/>.
- Executing the following code snippet from a UNIX command shell will
- rectify the problem if your Bugzilla installation is intended for an
- English-speaking audience. As always, be sure your Bugzilla
- installation has a good backup before making changes, and I recommend
- you understand what the script is doing before executing it.</para>
+ Making the change below will fix the problem if your installation is for
+ an English speaking audience.
+ </para>
<para>Telling Bugzilla to output a charset as part of the HTTP header is
much easier in version 2.18 and higher<![%bz-devel;[ (including any cvs
- pull after 4-May-2003 and development release after 2.17.5)]]>. Simply
- locatate the following line in <filename>Bugzilla/CGI.pm</filename>:
+ pull after 4-May-2003 and development release after 2.17.5)]]> than it was
+ in previous versions. Simply locate the following line in
+ <filename>Bugzilla/CGI.pm</filename>:
<programlisting>
# Make sure that we don't send any charset headers
$self->charset('');