You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Rob Hartill <ro...@imdb.com> on 1996/11/21 00:51:42 UTC
1.2b1 status
Features:
-=-=-=-=-=-=
Sameer has offered a patch to do unbuffered CGI.
Ben has said he supports the feature.
Bugs:
-=-=-=-=-=-
SIGUSR1/graceful restarts
Problem: Under FreeBSD, this is lethal. USR1 followed by HUP takes down
te server. Paul S (?) reported annoying processes after a USR1.
To do: Is there any documentation on this ? If there is, add a huge
warning.
patch to warn people away (via comments) committed.
bug confirmed by Brian on BSDI.
I think the current state of the code is all we're going to end up
with for 1.2b1 - hopefully some kind soul out there will look into
it and provide a patch after release. Documenting it is all that
really can be done now.
-=-=-=--=-=-=-
SSI causes bytes sent count to be waaay too low.
For each SSI include, apache subtracts bytes sent so far from
its counter (thinking bytes sent so far = headers only)
patch waiting for one more +1
-=-=-=-=--=--==
From: Roy
The problem is that a request on /dir/ is internally redirected to
/dir/index.html, which properly results in a 304 Not Modified. However,
the r->status is not updated to reflect new->status (and anything else
that might need to be promoted).
we're still waiting for someone to speak up on whether it's a
major problem or not. I don't know that area of the code well
enough, though I can't say that promotion of error code from
sub-redirects has been a problem for me personally. Again, flag
it as a known bug is probably the best we can
do here, unless someone wants to speak up. [brian]
-=-=-=-=-=-=-=-=
1.2-dev still has this bug in it. get_client_block needs to
check for the -1 error case from the call to bread().
patch offered. positive feedback so far.
-=-=-=-=-=-=-=-=-
Roy's claim of CGI schitzo behavior and improper dealing with
CONTENT_LENGTH. This is a showstopper in my opinion until more
voices are heard.
Roy offers 2 options:
a) Assume it is only for old scripts. This requires changing mod_cgi
so that it rejects anything without a Content-Length (411 Length
Required) even if it is chunked, or at least anything that cannot
be read into a single buffer before execing the script.
b) Assume it is for new scripts and that old scripts will just never
see the HTTP/1.1 input (after all, no sane client would chunk an
x-www-url-encoded form). This requires changing get_client_block
so that it passes the chunk size and footer to the script.
Jim gave (b) a +1
Showstoppers:
SSI byte sent logging [solveable]
Roy's redirect bug, though he seems to be having 2nd thoughts now,
probably not a showstopper.
? get_client_block needs to check for the -1 (sounds nasty)
CGI dealing & CONTENT_LENGTH
TODO:
done ASAP Find a patch for 'satisfy' that works well (tried and tested)
(before feature freeze)
Prepare more documentation.
Resolve all outstanding bugs (see above).
done Nov 17 Feature freeze.
Nov 24 Create last pre-beta tarball (Randy?)
Test, test, test.
Report back with positive as well as negative comments.
Nov 30 Create 1.2b1 tarball.
" Update CVS to reflect 1.2b1 release.
Dec 1 Release 1.2b1.
" Put documentation online if there is any.
" Hand 1.2 management over.