You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by gs...@locus.apache.org on 2000/03/24 01:10:07 UTC
cvs commit: apache-site/info known_bugs.html
gstein 00/03/23 16:10:06
Modified: info known_bugs.html
Log:
holy crap... a lot of these pages are out of date. this is a quick fix
to this page, but a big-ass revamp is needed...
Obtained from: Zak Greant <za...@freeimages.com>
Revision Changes Path
1.13 +1 -1 apache-site/info/known_bugs.html
Index: known_bugs.html
===================================================================
RCS file: /home/cvs/apache-site/info/known_bugs.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- known_bugs.html 1999/02/03 15:30:01 1.12
+++ known_bugs.html 2000/03/24 00:10:06 1.13
@@ -16,7 +16,7 @@
<H1 ALIGN="CENTER">Known Bugs in Apache</H1>
The most up-to-date resource for bug tracking and information is the
-<A HREF="http://bugs.apache.org/index">Apache bug database</A>.
+<A HREF="http://bugs.apache.org/">Apache bug database</A>.
Significant bugs at release time will also be noted there.
If you are running a 1.3 beta release, or version 1.2.X or earlier
and think you have found a bug, please upgrade to 1.3. Many bugs
reading POST data and returning an error
Posted by Roger Espel Llima <es...@iagora.net>.
Hi,
I'm doing some module development with Apache 1.3.12 and mod_perl, and
I've come across an odd point of the handler API: if a ContentHandler
handles a POST, reads the data body, and then returns an error like
NOT_FOUND, then Apache gets stuck trying to read the data again while
cleaning up.
Looking with gdb, the problem happens at the C API level, and the
sequence of calls is: ap_die -> ap_discard_request_body ->
ap_setup_client_block, which resets r->remaining with the value of the
Content-length header again.
The workaround, which works fine here, is to set Content-length to 0
just before returning an error.
But I figured it might be worth pointing this out, so it can be
clarified for the 2.0 release... returning errors after parsing
parameters isn't an unusual thing to do, and my feeling is that the API
should support it.
Maybe ap_setup_client_block should be a NOP if it's called more than
once in the same request?
--
Roger Espel Llima, espel@iagora.net
http://www.iagora.com/~espel/index.html
Re: cvs commit: apache-site/info known_bugs.html
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
gstein@locus.apache.org wrote:
>
> holy crap... a lot of these pages are out of date. this is
> a quick fix to this page, but a big-ass revamp is needed...
:
> -<A HREF="http://bugs.apache.org/index">Apache bug database</A>.
> +<A HREF="http://bugs.apache.org/">Apache bug database</A>.
Um, no, the explicit inclusion of 'index' is intentional. It's
index.cgi, and it uses path-info. By getting rid of it requests
with no path-info will work, but subsequent requests (generated
by the script) will break because the script won't be invoked --
the server will look at the path-info as a unique filename.
--
#ken P-)}
Ken Coar <http://Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed" <http://ApacheUnleashed.Com/>
Re: cvs commit: apache-site/info known_bugs.html
Posted by Greg Stein <gs...@lyra.org>.
Oh, geez. I just hit the "Background Information" link from the main
Apache HTTPd page. Some comments to note:
"Some existing prominent web servers have already switched to Apache
code ..."
Yah, right. Like the fact that over 60% of the public web sites run Apache
isn't good enough? :-)
"Apache version 1.3.4 is currently available to everyone, and is the most
stable version."
Heh.
Oh, and the list of sites: www.apache.org/info/apache_users.html. Somebody
is kidding, right? :-)
Cheers,
-g
p.s. yah, I know... I should go in an fix these things rather than
complain. maybe I will when I run out of coding steam some night... (but I
hope some other people will also help with sorting out the mess known as
our web site :-)
On Thu, 23 Mar 2000, Greg Stein wrote:
> This "known_bugs" page is woefully out of date. Also, it doesn't mention
> 2.0 bug reporting. The stuff in www.apache.org/info/ all looks out of date
> (a security report against 1.2.5?!?) ... etc
>
> If anybody wants to take a break from some coding, I think there is a lot
> of cruft in the apache-site repository that could be cleaned up.
>
> Cheers,
> -g
>
> On 24 Mar 2000 gstein@locus.apache.org wrote:
> > gstein 00/03/23 16:10:06
> >
> > Modified: info known_bugs.html
> > Log:
> > holy crap... a lot of these pages are out of date. this is a quick fix
> > to this page, but a big-ass revamp is needed...
> > Obtained from: Zak Greant <za...@freeimages.com>
> >
> > Revision Changes Path
> > 1.13 +1 -1 apache-site/info/known_bugs.html
> >
> > Index: known_bugs.html
> > ===================================================================
> > RCS file: /home/cvs/apache-site/info/known_bugs.html,v
> > retrieving revision 1.12
> > retrieving revision 1.13
> > diff -u -r1.12 -r1.13
> > --- known_bugs.html 1999/02/03 15:30:01 1.12
> > +++ known_bugs.html 2000/03/24 00:10:06 1.13
> > @@ -16,7 +16,7 @@
> > <H1 ALIGN="CENTER">Known Bugs in Apache</H1>
> >
> > The most up-to-date resource for bug tracking and information is the
> > -<A HREF="http://bugs.apache.org/index">Apache bug database</A>.
> > +<A HREF="http://bugs.apache.org/">Apache bug database</A>.
> > Significant bugs at release time will also be noted there.
> > If you are running a 1.3 beta release, or version 1.2.X or earlier
> > and think you have found a bug, please upgrade to 1.3. Many bugs
> >
> >
> >
> >
>
> --
> Greg Stein, http://www.lyra.org/
>
--
Greg Stein, http://www.lyra.org/
Re: cvs commit: apache-site/info known_bugs.html
Posted by Greg Stein <gs...@lyra.org>.
This "known_bugs" page is woefully out of date. Also, it doesn't mention
2.0 bug reporting. The stuff in www.apache.org/info/ all looks out of date
(a security report against 1.2.5?!?) ... etc
If anybody wants to take a break from some coding, I think there is a lot
of cruft in the apache-site repository that could be cleaned up.
Cheers,
-g
On 24 Mar 2000 gstein@locus.apache.org wrote:
> gstein 00/03/23 16:10:06
>
> Modified: info known_bugs.html
> Log:
> holy crap... a lot of these pages are out of date. this is a quick fix
> to this page, but a big-ass revamp is needed...
> Obtained from: Zak Greant <za...@freeimages.com>
>
> Revision Changes Path
> 1.13 +1 -1 apache-site/info/known_bugs.html
>
> Index: known_bugs.html
> ===================================================================
> RCS file: /home/cvs/apache-site/info/known_bugs.html,v
> retrieving revision 1.12
> retrieving revision 1.13
> diff -u -r1.12 -r1.13
> --- known_bugs.html 1999/02/03 15:30:01 1.12
> +++ known_bugs.html 2000/03/24 00:10:06 1.13
> @@ -16,7 +16,7 @@
> <H1 ALIGN="CENTER">Known Bugs in Apache</H1>
>
> The most up-to-date resource for bug tracking and information is the
> -<A HREF="http://bugs.apache.org/index">Apache bug database</A>.
> +<A HREF="http://bugs.apache.org/">Apache bug database</A>.
> Significant bugs at release time will also be noted there.
> If you are running a 1.3 beta release, or version 1.2.X or earlier
> and think you have found a bug, please upgrade to 1.3. Many bugs
>
>
>
>
--
Greg Stein, http://www.lyra.org/