From a522277200d67fce50cf686910abc397a3368ebf Mon Sep 17 00:00:00 2001 From: "jake%bugzilla.org" <> Date: Fri, 4 Apr 2008 11:46:41 +0000 Subject: Refix bug 201955 - Forgot to edit one of the introductory paragraphs and fixed a couple other minor errors. --- docs/en/xml/installation.xml | 18 ++++++++---------- 1 file 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 @@ - + Installation @@ -1065,8 +1065,7 @@ man 5 crontab -
+
Preventing untrusted Bugzilla content from executing malicious Javascript code @@ -1077,16 +1076,15 @@ man 5 crontab requirements mentioned in . - 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. + Making the change below will fix the problem if your installation is for + an English speaking audience. + Telling Bugzilla to output a charset as part of the HTTP header is much easier in version 2.18 and higher. Simply - locatate the following line in Bugzilla/CGI.pm: + pull after 4-May-2003 and development release after 2.17.5)]]> than it was + in previous versions. Simply locate the following line in + Bugzilla/CGI.pm: # Make sure that we don't send any charset headers $self->charset(''); -- cgit v1.2.3-24-g4f1b