cvs commit: apache-site bug_report.html security_report.html
coar98/09/23 08:42:42 Modified:.bug_report.html security_report.html Log: The CERT points to our bug-report page, so make it clear how to let us know about security issues. Revision ChangesPath 1.19 +8 -5 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- bug_report.html 1998/08/11 03:19:15 1.18 +++ bug_report.html 1998/09/23 15:42:40 1.19 @@ -12,9 +12,15 @@ IMG SRC=images/apache_sub.gif ALT= -H2Apache Bug Reporting Page/H2 +H1Apache Bug Reporting Page/H1 -PWelcome to the Apache Bug Reporting Page! If you are having trouble +BLOCKQUOTE +STRONGReports of security issues should EMnot/EM be reported here. +Please see the A HREF=security_report.htmlsecurity report page/A +if you have concerns or think you have discovered a security hole in +the Apache Web server software./STRONG +/BLOCKQUOTE +PIf you are having trouble with Apache, please fill out a problem report form and submit it. Before you do that, though, FONT COLOR=redmake STRONGsure/STRONG you have done STRONGall/STRONG of the following:/FONT/P @@ -96,9 +102,6 @@ /FORM P H1Do NOT send configuration questions or requests for help debugging CGI!/H1 - -pFolks wishing to report a security/denial of service bug may want to -visit a href=security_report.htmlthis page/a. /BODY /HTML 1.3 +1 -1 apache-site/security_report.html Index: security_report.html === RCS file: /export/home/cvs/apache-site/security_report.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- security_report.html 1998/09/07 03:22:04 1.2 +++ security_report.html 1998/09/23 15:42:41 1.3 @@ -22,7 +22,7 @@ STRONGWe cannot accept regular bug reports or other queries at this address, we ask that you use our a href=bug_report.htmlbug reporting page/a for those. FONT color=redAll mail sent to -this address that is not reporting a security hole will be ignored. +this address that does not relate to security issues will be ignored. /FONT/STRONG pNote that all networked servers are subject to denial of service
cvs commit: apache-site bug_report.html
brian 98/07/02 18:03:59 Modified:.bug_report.html Log: Show me a browser without form support and I'll show you a user we shouldn't bother with. Revision ChangesPath 1.16 +0 -4 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- bug_report.html 1998/06/06 02:57:10 1.15 +++ bug_report.html 1998/07/03 01:03:58 1.16 @@ -92,10 +92,6 @@ INPUT TYPE=submit VALUE=Search for/submit a problem report /FORM P -If your browser is incapable of using forms, please submit the same -information to -A HREF=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/A. -/P H1Do NOT send configuration questions or requests for help debugging CGI!/H1 /BODY /HTML
cvs commit: apache-site bug_report.html info.html
brian 98/06/05 19:57:12 Modified:.bug_report.html info.html Log: update for 1.3 release. Revision ChangesPath 1.15 +3 -3 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- bug_report.html 1998/05/12 05:58:02 1.14 +++ bug_report.html 1998/06/06 02:57:10 1.15 @@ -21,8 +21,8 @@ OL LIVerified that the bug exists in A HREF=mirrors/the most recent - version/A of Apache. There are many bugs in the 1.1/tree that have been - fixed in the 1.2 tree. + version/A of Apache. There are many bugs in the 1.2 version and earlier + that have been fixed in the 1.3 version. /LI LIChecked the A HREF=info/known_bugs.htmlknown bugs/A page. /LI @@ -45,7 +45,7 @@ /LI LIChecked the A HREF=docs/misc/FAQ.htmlFAQ/A. /LI - LIIf upgrading to 1.3 (currently in beta), checked the + LIIf upgrading to 1.3, checked the A HREF=docs/upgrading_to_1_3.htmlUpgrading to 1.3/A notes. /LI LISearched the A HREF=http://bugs.apache.org/;bug report/A 1.13 +2 -2 apache-site/info.html Index: info.html === RCS file: /export/home/cvs/apache-site/info.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- info.html 1998/05/31 10:30:25 1.12 +++ info.html 1998/06/06 02:57:10 1.13 @@ -98,8 +98,8 @@ Apache is being maintained./P H2When will Apache be available?/H2 -PApache version 1.2.6 is currently available to everyone, and is -the most stable version. Apache 1.3 is currently in beta. +PApache version 1.3.0 is currently available to everyone, and is +the most stable version. H2Will Apache be supported?/H2
cvs commit: apache-site bug_report.html
coar98/04/09 16:26:27 Modified:.bug_report.html Log: Include pointers to the upgrade notes (almost FAQs), and correct the bugdb pointer. Revision ChangesPath 1.12 +7 -1 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- bug_report.html 1998/03/26 11:54:53 1.11 +++ bug_report.html 1998/04/09 23:26:26 1.12 @@ -45,7 +45,13 @@ /LI LIChecked the A HREF=docs/misc/FAQ.htmlFAQ/A. /LI - LISearched the A HREF=http://www.apache.org/bugdb.cgi;bug report/A + LIIf upgrading to 1.2 (any version), checked the + A HREF=docs/upgrading_to_1_2.htmlUpgrading to 1.2/A notes. + /LI + LIIf upgrading to 1.3 (currently in beta), checked the + A HREF=docs/upgrading_to_1_3.htmlUpgrading to 1.3/A notes. + /LI + LISearched the A HREF=http://bugs.apache.org/;bug report/A database. When you are doing this, you should be sure to search closed problem reports in addition to open ones. Also note that the search is not keyword based, so it requires an exact match
cvs commit: apache-site bug_report.html
coar98/04/09 16:29:47 Modified:.bug_report.html Log: Nuts, there *isn't* an upgrading_to_1_2 file [any more]. Revision ChangesPath 1.13 +0 -3 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- bug_report.html 1998/04/09 23:26:26 1.12 +++ bug_report.html 1998/04/09 23:29:47 1.13 @@ -45,9 +45,6 @@ /LI LIChecked the A HREF=docs/misc/FAQ.htmlFAQ/A. /LI - LIIf upgrading to 1.2 (any version), checked the - A HREF=docs/upgrading_to_1_2.htmlUpgrading to 1.2/A notes. - /LI LIIf upgrading to 1.3 (currently in beta), checked the A HREF=docs/upgrading_to_1_3.htmlUpgrading to 1.3/A notes. /LI
cvs commit: apache-site bug_report.html
coar98/03/26 03:54:53 Modified:.bug_report.html Log: Some HTML cleanup. (There should be *no* leading space inside anchor text; it gives the highlighted link a tail. It's a SHOULD in the HTML specs for browsers to ignore \w*$\w* between a container start-tag and the first non-whitespace content character, but most browsers ignore this. Hence no newlines or whitespace between LI or A HREF and the text that follows.) Revision ChangesPath 1.11 +46 -35apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- bug_report.html 1998/03/25 23:47:31 1.10 +++ bug_report.html 1998/03/26 11:54:53 1.11 @@ -16,43 +16,52 @@ PWelcome to the Apache Bug Reporting Page! If you are having trouble with Apache, please fill out a problem report form and submit it. -Before you do that, though, FONT COLOR=redmake bsure/b you have -done ball/b of the following:/FONT/P +Before you do that, though, FONT COLOR=redmake STRONGsure/STRONG you +have done STRONGall/STRONG of the following:/FONT/P OL -LIVerified that the bug exists in A href=mirrors/the most recent version/A -of Apache. There are many bugs in the 1.1/tree that have been fixed -in the 1.2 tree. -LIChecked the A href=docs/misc/known_bugs.htmlknown bugs/A page. -LIChecked the A HREF=docs/misc/known_client_problems.htmlknown client problems/A page. -LIChecked the A href=docs/misc/compat_notes.htmlcompatibility -notes/A page. -LIFollowed the instructions in the codeINSTALL/code file correctly - -you edited the codeConfiguration/code file to set the right platform -and ran the codeConfigure/code script to create the new -codeMakefile/code. -LITried compiling with only the distributed set of modules and with -no other patches (so that we can make sure it's an Apache bug and -not a bug in a module or patch provided by someone else). It is -frustrating to take time and effort to track down a problem only -to figure out it caused by a broken third party module. -LIChecked the A HREF=docs/misc/FAQ.htmlFAQ/A. -LISearched the A HREF=http://www.apache.org/bugdb.cgi;bug report/A -database. When you are doing this, you should be sure to search -closed problem reports in addition to open ones. Also note that -the search is not keyword based, so it requires an exact match -of what you enter to find anything. + LIVerified that the bug exists in A HREF=mirrors/the most recent + version/A of Apache. There are many bugs in the 1.1/tree that have been + fixed in the 1.2 tree. + /LI + LIChecked the A HREF=docs/misc/known_bugs.htmlknown bugs/A page. + /LI + LIChecked the A HREF=docs/misc/known_client_problems.htmlknown client + problems/A page. + /LI + LIChecked the A HREF=docs/misc/compat_notes.htmlcompatibility + notes/A page. + /LI + LIFollowed the instructions in the CODEINSTALL/CODE file correctly - + you edited the CODEConfiguration/CODE file to set the right platform + and ran the CODEConfigure/CODE script to create the new + CODEMakefile/CODE. + /LI + LITried compiling with only the distributed set of modules and with + no other patches (so that we can make sure it's an Apache bug and + not a bug in a module or patch provided by someone else). It is + frustrating to take time and effort to track down a problem only + to figure out it caused by a broken third party module. + /LI + LIChecked the A HREF=docs/misc/FAQ.htmlFAQ/A. + /LI + LISearched the A HREF=http://www.apache.org/bugdb.cgi;bug report/A + database. When you are doing this, you should be sure to search + closed problem reports in addition to open ones. Also note that + the search is not keyword based, so it requires an exact match + of what you enter to find anything. + /LI /OL BLOCKQUOTE STRONG If you're not sure that your problem is specifically related to a - bug in Apache (ie. not something like a client problem or configuration - problem), we strongly recommend that you check in the - A HREF=news:comp.infosystems.www.servers.unix;SAMP - comp.infosystems.www.servers.unix/SAMP/A or A HREF= - news:comp.infosystems.www.servers.ms-windows;SAMP - comp.infosystems.www.servers.ms-windows/SAMP/A (depending on + bug in Apache (EMi.e./EM, not something like a client problem or + configuration problem), we strongly recommend that you check in the + A HREF=news:comp.infosystems.www.servers.unix; + SAMPcomp.infosystems.www.servers.unix/SAMP/A or + A HREF=news:comp.infosystems.www.servers.ms-windows; +
cvs commit: apache-site bug_report.html
marc98/03/24 21:05:14 Modified:.bug_report.html Log: Let's shout even louder at people about submitting bug reports. Revision ChangesPath 1.9 +9 -3 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- bug_report.html 1997/11/08 23:29:59 1.8 +++ bug_report.html 1998/03/25 05:05:13 1.9 @@ -16,8 +16,8 @@ PWelcome to the Apache Bug Reporting Page! If you are having trouble with Apache, please fill out a problem report form and submit it. -Before you do that, though, make bsure/b you have done ball/b -of the following:/P +Before you do that, though, FONT COLOR=redmake bsure/b you have +done ball/b of the following:/FONT/P OL LIVerified that the bug exists in A href=mirrors/the most recent version/A @@ -33,7 +33,9 @@ codeMakefile/code. LITried compiling with only the distributed set of modules and with no other patches (so that we can make sure it's an Apache bug and -not a bug in a module or patch provided by someone else). +not a bug in a module or patch provided by someone else). It is +frustrating to take time and effort to track down a problem only +to figure out it caused by a broken third party module. LIChecked the A HREF=docs/misc/FAQ.htmlFAQ/A. LISearched the A HREF=http://www.apache.org/bugdb.cgi;bug report/A database. When you are doing this, you should be sure to search @@ -56,6 +58,10 @@ and you will help keep developer time free for improving Apache. Most bug reports submitted are actually user configuration problems that could be easily fixed by asking in the newsgroup. + + PFONT COLOR=redDo Bnot/B post to Usenet and submit a bug + report at the same time./FONT This wastes everyone's time. + Post to Usenet and wait a few days. /STRONG /BLOCKQUOTE
cvs commit: apache-site bug_report.html
marc98/03/25 15:47:33 Modified:.bug_report.html Log: The world isn't Unix any more (not that it ever completely was), plus Deja News is cool. Revision ChangesPath 1.10 +15 -9 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- bug_report.html 1998/03/25 05:05:13 1.9 +++ bug_report.html 1998/03/25 23:47:31 1.10 @@ -49,15 +49,21 @@ If you're not sure that your problem is specifically related to a bug in Apache (ie. not something like a client problem or configuration problem), we strongly recommend that you check in the - A - HREF=news:comp.infosystems.www.servers.unix; - SAMPcomp.infosystems.www.servers.unix/SAMP/A - USENET newsgroup first. If you don't receive a response within a few - days, then please submit it to the Apache bug database. If it's a - known issue, you'll probably get a faster response from the newsgroup - and you will help keep developer time free for improving Apache. Most - bug reports submitted are actually user configuration problems that - could be easily fixed by asking in the newsgroup. + A HREF=news:comp.infosystems.www.servers.unix;SAMP + comp.infosystems.www.servers.unix/SAMP/A or A HREF= + news:comp.infosystems.www.servers.ms-windows;SAMP + comp.infosystems.www.servers.ms-windows/SAMP/A (depending on + the platform being used) Usenet newsgroup first. If you don't + receive a response within a few days, then please submit it to + the Apache bug database. If it's a known issue, you'll probably + get a faster response from the newsgroup and you will help keep + developer time free for improving Apache. Most bug reports submitted + are actually user configuration problems that could be easily + fixed by asking in the newsgroup. + + PIf you do not have access to a Usenet server, there are + several web sites on the Internet that allow you to read and post + to Usenet, such as A HREF=http://www.dejanews.com/;Deja News/A. PFONT COLOR=redDo Bnot/B post to Usenet and submit a bug report at the same time./FONT This wastes everyone's time.
cvs commit: apache-site bug_report.html
brian 97/11/08 15:29:59 Modified:.bug_report.html Log: Added a pointer to the known client problems page. Revision ChangesPath 1.8 +1 -0 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- bug_report.html 1997/08/03 10:11:06 1.7 +++ bug_report.html 1997/11/08 23:29:59 1.8 @@ -24,6 +24,7 @@ of Apache. There are many bugs in the 1.1/tree that have been fixed in the 1.2 tree. LIChecked the A href=docs/misc/known_bugs.htmlknown bugs/A page. +LIChecked the A HREF=docs/misc/known_client_problems.htmlknown client problems/A page. LIChecked the A href=docs/misc/compat_notes.htmlcompatibility notes/A page. LIFollowed the instructions in the codeINSTALL/code file correctly -
cvs commit: apache-site bug_report.html
marc97/05/11 10:24:52 Modified:. bug_report.html Log: Another small step in the futile fight against garbage PRs... Revision ChangesPath 1.5 +7 -3 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.4 retrieving revision 1.5 diff -C3 -r1.4 -r1.5 *** bug_report.html 1997/04/17 21:59:01 1.4 --- bug_report.html 1997/05/11 17:24:51 1.5 *** *** 8,18 PWelcome to the Apache Bug Reporting Page! If you are having trouble with Apache, please fill out a problem report form and submit it. ! Before you do that, though, make bsure/b you have:/P OL LIVerified that the bug exists in A href=dist/the most recent version/A ! of Apache. LIChecked the A href=docs/misc/known_bugs.htmlknown bugs/A page. LIChecked the A href=docs/misc/compat_notes.htmlcompatibility notes/A page. --- 8,20 PWelcome to the Apache Bug Reporting Page! If you are having trouble with Apache, please fill out a problem report form and submit it. ! Before you do that, though, make bsure/b you have done ball/b ! of the following:/P OL LIVerified that the bug exists in A href=dist/the most recent version/A ! of Apache. There are many bugs in the 1.1 tree that have been fixed ! in the 1.2 tree. LIChecked the A href=docs/misc/known_bugs.htmlknown bugs/A page. LIChecked the A href=docs/misc/compat_notes.htmlcompatibility notes/A page. *** *** 42,48 USENET newsgroup first. If you don't receive a response within a few days, then please submit it to the Apache bug database. If it's a known issue, you'll probably get a faster response from the newsgroup ! and you will help keep developer time free for improving Apache. /STRONG /BLOCKQUOTE --- 44,52 USENET newsgroup first. If you don't receive a response within a few days, then please submit it to the Apache bug database. If it's a known issue, you'll probably get a faster response from the newsgroup ! and you will help keep developer time free for improving Apache. Most ! bug reports submitted are actually user configuration problems that ! could be easily fixed by asking in the newsgroup. /STRONG /BLOCKQUOTE
cvs commit: apache-site bug_report.html
marc97/04/17 14:59:02 Modified:. bug_report.html Log: Expand on things to check before submitting a PR. Revision ChangesPath 1.4 +19 -15apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.3 retrieving revision 1.4 diff -C3 -r1.3 -r1.4 *** bug_report.html 1997/03/27 20:05:18 1.3 --- bug_report.html 1997/04/17 21:59:01 1.4 *** *** 7,21 H2Apache Bug Reporting Page/H2 PWelcome to the Apache Bug Reporting Page! If you are having trouble ! with Apache, ! please fill out a problem report form and submit it. Before you do ! that, though, make ! bsure/b ! you have:/P OL ! LIMade sure the bug exists in A href=dist/the most recent version/A of ! Apache. LIChecked the A href=docs/misc/known_bugs.htmlknown bugs/A page. LIChecked the A href=docs/misc/compat_notes.htmlcompatibility notes/A page. --- 7,18 H2Apache Bug Reporting Page/H2 PWelcome to the Apache Bug Reporting Page! If you are having trouble ! with Apache, please fill out a problem report form and submit it. ! Before you do that, though, make bsure/b you have:/P OL ! LIVerified that the bug exists in A href=dist/the most recent version/A ! of Apache. LIChecked the A href=docs/misc/known_bugs.htmlknown bugs/A page. LIChecked the A href=docs/misc/compat_notes.htmlcompatibility notes/A page. *** *** 23,49 you edited the codeConfiguration/code file to set the right platform and ran the codeConfigure/code script to create the new codeMakefile/code. ! LITried compiling with only the distributed set of modules (so that we ! can make sure ! it's an Apache bug and not a bug in a module provided by someone else). /OL BLOCKQUOTE STRONG ! If you're not sure whether your problem is specifically related to ! Apache, we strongly recommend that you check in the A HREF=news:comp.infosystems.www.servers.unix; SAMPcomp.infosystems.www.servers.unix/SAMP/A USENET newsgroup first. If you don't receive a response within a few days, then please submit it to the Apache bug database. If it's a ! known issue, you'll probably get a faster response from the newsgroup. /STRONG /BLOCKQUOTE PIf you have done all of the preceding, then please select the button ! below and fill out the form, ! and we will respond to it as soon as we can. /P FORM ACTION=http://www.apache.org/bugdb.cgi; INPUT TYPE=submit VALUE=Search for/submit a problem report --- 20,53 you edited the codeConfiguration/code file to set the right platform and ran the codeConfigure/code script to create the new codeMakefile/code. ! LITried compiling with only the distributed set of modules and with ! no other patches (so that we can make sure it's an Apache bug and ! not a bug in a module or patch provided by someone else). ! LIChecked the A HREF=docs/misc/FAQ.htmlFAQ/A. ! LISearched the A HREF=http://www.apache.org/bugdb.cgi;bug report/A ! database. When you are doing this, you should be sure to search ! closed problem reports in addition to open ones. Also note that ! the search is not keyword based, so it requires an exact match ! of what you enter to find anything. /OL BLOCKQUOTE STRONG ! If you're not sure that your problem is specifically related to a ! bug in Apache (ie. not something like a client problem or configuration ! problem), we strongly recommend that you check in the A HREF=news:comp.infosystems.www.servers.unix; SAMPcomp.infosystems.www.servers.unix/SAMP/A USENET newsgroup first. If you don't receive a response within a few days, then please submit it to the Apache bug database. If it's a ! known issue, you'll probably get a faster response from the newsgroup ! and you will help keep developer time free for improving Apache. /STRONG /BLOCKQUOTE PIf you have done all of the preceding, then please select the button ! below and fill out the form, and we will respond to it as soon as we can. /P FORM ACTION=http://www.apache.org/bugdb.cgi; INPUT TYPE=submit VALUE=Search for/submit a problem report
cvs commit: apache-site bug_report.html
dgaudet 97/03/27 12:05:20 Modified:. bug_report.html Log: Tweaks suggested by Marc. Submitted by: Ken Coar Revision ChangesPath 1.3 +15 -1 apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C3 -r1.2 -r1.3 *** bug_report.html 1997/03/25 04:58:25 1.2 --- bug_report.html 1997/03/27 20:05:18 1.3 *** *** 8,14 PWelcome to the Apache Bug Reporting Page! If you are having trouble with Apache, ! please fill this out and submit it. Before you do that, though, make bsure/b you have:/P --- 8,15 PWelcome to the Apache Bug Reporting Page! If you are having trouble with Apache, ! please fill out a problem report form and submit it. Before you do ! that, though, make bsure/b you have:/P *** *** 26,31 --- 27,45 can make sure it's an Apache bug and not a bug in a module provided by someone else). /OL + + BLOCKQUOTE + STRONG + If you're not sure whether your problem is specifically related to + Apache, we strongly recommend that you check in the + A +HREF=news:comp.infosystems.www.servers.unix; + SAMPcomp.infosystems.www.servers.unix/SAMP/A + USENET newsgroup first. If you don't receive a response within a few + days, then please submit it to the Apache bug database. If it's a + known issue, you'll probably get a faster response from the newsgroup. + /STRONG + /BLOCKQUOTE PIf you have done all of the preceding, then please select the button below and fill out the form,
cvs commit: apache-site bug_report.html
dgaudet 97/03/24 20:58:26 Modified:. bug_report.html Log: Bug reporting changes to direct people to the GNATS system. Reviewed by:Dean Gaudet, Roy Fielding Submitted by: Ken Coar Revision ChangesPath 1.2 +26 -82apache-site/bug_report.html Index: bug_report.html === RCS file: /export/home/cvs/apache-site/bug_report.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C3 -r1.1 -r1.2 *** bug_report.html 1997/03/25 04:43:15 1.1 --- bug_report.html 1997/03/25 04:58:25 1.2 *** *** 6,100 IMG SRC=images/apache_sub.gif ALT= H2Apache Bug Reporting Page/H2 ! PWelcome to the Apache Bug Reporting Page! If you are having trouble with Apache, ! please fill this out and submit it. Before you do that, though, make bsure/b you have:/P OL LIMade sure the bug exists in A href=dist/the most recent version/A of ! Apache. LIChecked the A href=docs/misc/known_bugs.htmlknown bugs/A page. ! LIChecked the A href=docs/misc/compat_notes.htmlcompatibility notes/A page. LIFollowed the instructions in the codeINSTALL/code file correctly - you edited the codeConfiguration/code file to set the right platform ! and ran the codeConfigure/code script to create the new codeMakefile/code. ! LITried compiling with only the distributed set of modules (so that we can make sure ! it's an apache bug and not a bug in a module provided by someone else). /OL ! H3Note: we already know about the problem interactions between AOL's ! proxies and Apache 1.2's use of HTTP/1.1. We are working with AOL to ! help them fix their problems./H3 ! ! PIf you have done all of the preceding, then fill out the form below, ! and we will respond to it as soon as we can. If your browser is ! incapable of using forms, please submit the same information to A ! href=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/A./P ! ! H1Do NOT send configuration questions or requests for help debugging CGI !!/H1 ! ! P ! ! FORM METHOD=POST ACTION=http://www.apache.org/bugs.cgi; ! ! Your email address: input type=text name=emailaddy size=15BR ! ! Quick, one-line summary of the problem:BR ! input type=text name=summary size=45BR ! ! Operating system: SELECT NAME=platform ! OPTIONAIX ! OPTIONApollo ! OPTIONA/UX ! OPTIONBSDI ! OPTIONFreeBSD ! OPTIONHPUX ! OPTIONIrix ! OPTIONLinux ! OPTIONNeXT ! OPTIONNetBSD ! OPTIONOS/2 ! OPTIONOSF/1 ! OPTIONSCO ! OPTION SELECTEDSolaris 2.x ! OPTIONSunOS 4.x ! OPTIONUltrix ! OPTIONUnixWare ! OPTIONOTHER: ! /SELECTBR ! Operating system, if other: input type=text name=other size=5 ! OS Version: input type=text name=version size=5br ! Version of Apache being used: input type=text name=aversion size-5BR ! ! Extra modules used: input type=text name=modules size=45 ! ! P ! ! What are the symptoms of the bug you are seeing?BR ! ! textarea rows=10 cols=50 name=symptoms/textarea ! ! P ! ! If you have a URL to an object which exhibits this bug, ! please post it here:BR ! ! input type=text name=urlprob size=50 ! ! P ! ! If the bug created a core file, and you have codegdb/code or ! codedbx/code installed, please do a backtrace showing where the ! segmentation fault occured, and paste that in right here:BR ! ! textarea rows=10 cols=50 name=backtrace/textarea ! ! P ! ! input type=submit value=Submit bug report ! ! P ! /FORM ! ! /BODY/HTML --- 6,44 IMG SRC=images/apache_sub.gif ALT= H2Apache Bug Reporting Page/H2 ! PWelcome to the Apache Bug Reporting Page! If you are having trouble ! with Apache, ! please fill this out and submit it. Before you do that, though, make ! bsure/b you have:/P OL LIMade sure the bug exists in A href=dist/the most recent version/A of ! Apache. LIChecked the A href=docs/misc/known_bugs.htmlknown bugs/A page. ! LIChecked the A href=docs/misc/compat_notes.htmlcompatibility ! notes/A page. LIFollowed the instructions in the codeINSTALL/code file correctly - you edited the codeConfiguration/code file to set the right platform ! and ran the codeConfigure/code script to create the new ! codeMakefile/code. ! LITried compiling with only the distributed set of modules (so that we ! can make sure ! it's an Apache bug and not a bug in a module provided by someone else). /OL ! PIf you have done all of the preceding, then please select the button ! below and fill out the form, ! and we will respond to it as soon as we can. ! /P ! FORM ACTION=http://www.apache.org/bugdb.cgi; ! INPUT TYPE=submit VALUE=Search for/submit a
