change a couple of 'id' values that produce pages that some mirrors get tripped up on.

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@62913 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
jim winstead 2001-11-21 01:48:33 +00:00
parent 91848c237f
commit 7d4812b1d1
3 changed files with 16 additions and 16 deletions

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.34 $ -->
<!-- $Revision: 1.35 $ -->
<chapter id="security">
<title>Security</title>
@ -86,10 +86,10 @@
</simpara>
</sect1>
<sect1 id="security.cgi">
<sect1 id="security.cgi-bin">
<title>Installed as CGI binary</title>
<sect2 id="security.cgi.attacks">
<sect2 id="security.cgi-bin.attacks">
<title>Possible attacks</title>
<simpara>
Using PHP as a <acronym>CGI</acronym> binary is an option for
@ -161,7 +161,7 @@
</itemizedlist>
</sect2>
<sect2 id="security.cgi.default">
<sect2 id="security.cgi-bin.default">
<title>Case 1: only public files served</title>
<simpara>
@ -185,7 +185,7 @@
</simpara>
</sect2>
<sect2 id="security.cgi.force-redirect">
<sect2 id="security.cgi-bin.force-redirect">
<title>Case 2: using --enable-force-cgi-redirect</title>
<simpara>
This compile-time option prevents anyone from calling PHP
@ -213,7 +213,7 @@ AddHandler php-script .php
</simpara>
</sect2>
<sect2 id="security.cgi.doc-root">
<sect2 id="security.cgi-bin.doc-root">
<title>Case 3: setting doc_root or user_dir</title>
<simpara>
To include active content, like scripts and executables, in the
@ -273,7 +273,7 @@ AddHandler php-script .php
</simpara>
</sect2>
<sect2 id="security.cgi.shell">
<sect2 id="security.cgi-bin.shell">
<title>Case 4: PHP parser outside of web tree</title>
<para>
A very secure option is to put the PHP parser binary somewhere

View file

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.75 $ -->
<reference id="ref.var">
<!-- $Revision: 1.76 $ -->
<reference id="ref.variables">
<title>Variable Functions</title>
<titleabbrev>Variables</titleabbrev>

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.34 $ -->
<!-- $Revision: 1.35 $ -->
<chapter id="security">
<title>Security</title>
@ -86,10 +86,10 @@
</simpara>
</sect1>
<sect1 id="security.cgi">
<sect1 id="security.cgi-bin">
<title>Installed as CGI binary</title>
<sect2 id="security.cgi.attacks">
<sect2 id="security.cgi-bin.attacks">
<title>Possible attacks</title>
<simpara>
Using PHP as a <acronym>CGI</acronym> binary is an option for
@ -161,7 +161,7 @@
</itemizedlist>
</sect2>
<sect2 id="security.cgi.default">
<sect2 id="security.cgi-bin.default">
<title>Case 1: only public files served</title>
<simpara>
@ -185,7 +185,7 @@
</simpara>
</sect2>
<sect2 id="security.cgi.force-redirect">
<sect2 id="security.cgi-bin.force-redirect">
<title>Case 2: using --enable-force-cgi-redirect</title>
<simpara>
This compile-time option prevents anyone from calling PHP
@ -213,7 +213,7 @@ AddHandler php-script .php
</simpara>
</sect2>
<sect2 id="security.cgi.doc-root">
<sect2 id="security.cgi-bin.doc-root">
<title>Case 3: setting doc_root or user_dir</title>
<simpara>
To include active content, like scripts and executables, in the
@ -273,7 +273,7 @@ AddHandler php-script .php
</simpara>
</sect2>
<sect2 id="security.cgi.shell">
<sect2 id="security.cgi-bin.shell">
<title>Case 4: PHP parser outside of web tree</title>
<para>
A very secure option is to put the PHP parser binary somewhere