coar 98/02/11 07:14:37 Modified: htdocs/manual/misc FAQ.html compat_notes.html known_bugs.html security_tips.html Log: Clean up some references to "bugdb.cgi". Revision Changes Path 1.106 +4 -4 apache-1.3/htdocs/manual/misc/FAQ.html Index: FAQ.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v retrieving revision 1.105 retrieving revision 1.106 diff -u -r1.105 -r1.106 --- FAQ.html 1998/02/05 09:58:38 1.105 +++ FAQ.html 1998/02/11 15:14:33 1.106 @@ -15,7 +15,7 @@
- $Revision: 1.105 $ ($Date: 1998/02/05 09:58:38 $) + $Revision: 1.106 $ ($Date: 1998/02/11 15:14:33 $)
The latest version of this FAQ is always available from the main @@ -482,7 +482,7 @@ Most problems that get reported to The Apache Group are recorded in the bug database. Please check the existing reports, open and closed, before adding one. If you find @@ -516,7 +516,7 @@ have obtained no relief, then please do let The Apache Group know about the problem by logging a bug report.
@@ -1564,7 +1564,7 @@ issues is the cause of your problem, and it hasn't been reported before, please submit a problem report. Be sure to include complete details, such as the compiler & OS versions and exact error messages. 1.19 +1 -1 apache-1.3/htdocs/manual/misc/compat_notes.html Index: compat_notes.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/compat_notes.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- compat_notes.html 1998/01/26 16:53:49 1.18 +++ compat_notes.html 1998/02/11 15:14:34 1.19 @@ -22,7 +22,7 @@ scratch, so certain liberties the earlier servers took may not be available here. These are all easily fixable. If you know of other non-fatal problems that belong here, let us know. +HREF="http://www.apache.org/bug_report.html">let us know.
Please also check the known bugs
page, and the known client
1.43 +11 -11 apache-1.3/htdocs/manual/misc/known_bugs.html
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/known_bugs.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- known_bugs.html 1998/02/09 18:32:33 1.42
+++ known_bugs.html 1998/02/11 15:14:35 1.43
@@ -16,7 +16,7 @@
Known Bugs in Apache
The most up-to-date resource for bug tracking and information is the
-Apache bug database.
+Apache bug database.
Significant bugs at release time will also be noted there.
If you are running a 1.2 beta release or version 1.1.3 or earlier
and think you have found a bug, please upgrade to 1.2. Many bugs
@@ -119,7 +119,7 @@
USE_xxxxx_SERIALIZED_ACCEPT definitions, see the
conf.h for your architecture.
This is being tracked as
To resolve this problem, we are adding one of the above settings to the default settings for platforms as we discover which is appropriate for them. New as of 1.3b3: the server will @@ -131,7 +131,7 @@
%2f. This will be tracked as - PR#543. + PR#543.
"mod_include.c", line 1123: warning: end-of-loop code not reached. This is a bogus warning and can be ignored. - See PR#681. + See PR#681.
Configuration. See - PR#616 + PR#616 and the Apache FAQ. This is not a bug in Apache. @@ -169,7 +169,7 @@
created shared memory segment #730499" in error_log is not an error and should be ignored. See - PR#696. + PR#696.
@@ -194,7 +194,7 @@ descriptor slack workaround
This problem was tracked as - PR#832. + PR#832.
@@ -215,7 +215,7 @@ There appears to be a problem on BSDI 2.1 with large numbers of virtual hosts. This appears similar to a file-descriptor limit but BSDI should not have this problem. This will be tracked as - PR#611. + PR#611. See also the Apache FAQ.
@@ -234,12 +234,12 @@ fixes this problem. It also fixes the problem which makes Apache pick the last equally acceptable variant instead of the first. This will be tracked as - PR#94. + PR#94.
Compilation fails on SCO3 when using gcc instead of cc, complaining
gcc: noinline: No such file or directory". Fix
- is given in PR#695.
+ is given in PR#695.
Please send any other useful security tips to The Apache Group by filling out a -problem report, or by +problem report, or by sending mail to email@example.com