dougm 02/03/24 15:54:32
Modified: . STATUS
Log:
various updates
Revision Changes Path
1.13 +127 -98 modperl/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/modperl/STATUS,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- STATUS 24 Mar 2002 23:01:33 -0000 1.12
+++ STATUS 24 Mar 2002 23:54:32 -0000 1.13
@@ -1,59 +1,28 @@
mod_perl 1.3 STATUS:
- Last modified at [$Date: 2002/03/24 23:01:33 $]
+ Last modified at [$Date: 2002/03/24 23:54:32 $]
Release:
- 1.26-dev: In development.
- 1.25: Released July 11, 2001.
+ 1.27-dev: In development.
+ 1.26: Released July 11, 2001.
Available Patches:
- * $r->args parsing of one=&two=2
- Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=98018719907031&w=2
- Status:
- patch available at
- http://marc.theaimsgroup.com/?l=apache-modperl&m=98048943129379&w=2
+Needs Patch or Further Investigation
* two identical directives in <Perl> configuration
Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=97449481013350&w=2
Status:
doc patch at
http://marc.theaimsgroup.com/?l=apache-modperl&m=97450363501652&w=2
-
- * $r->finfo problem with HTML::Mason::ApacheHandler
- Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=96854561311519&w=2
- Status:
- may be fixed with
- http://marc.theaimsgroup.com/?l=apache-modperl&m=96869790426565&w=2
-
- * get/set handlers issues
- Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=95721313917562&w=2
- Status:
- patch available
- http://perl.apache.org/~dougm/set_handlers.pat
-
- * Apache::test
- Report:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=98278446807561&w=2
- Status:
- patch available
-
-Needs Patch or Further Investigation
+ however: this documented feature should be supported.
* readdir() broken on linux with glibc 2.2
Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=98824089613574&w=2
Status:
+ does anybody have an example to reproduce the bug?
- * SERVER_MERGE and DIR_MERGE
- Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=97351976714878&w=2
- Status:
- The require() part may be legitimate. personally, I never
- understood the DIR_CREATE happening before SERVER_CREATE
- either, but it doesn't seem to affect anything. the double
- DIR_MERGE is just a misunderstanding on Andy's part and is
- a result of how Apache handles <Location> before and
- after translation. --Geoff
-
* warn() going to the wrong log
Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=98190005604037&w=2
Status:
@@ -61,6 +30,15 @@
in a vhost when the vhost relies on the ErrorLog from the main
server --Geoff
+ s->error_fname == NULL is expected, see ap_open_logs(), only
+ s->error_log is inherited.
+
+ i would expect stderr to only ever be opened to the main
+ server log at startup. otherwise, we'd need to redirect stderr at the
+ start of every request and restore it at the end. seems expensive.
+ i would be suprised if this every worked as matt expected it
+ to. -dougm
+
* segfaults with DBI->connect (mysql)
Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=96392180616185&w=2
Status:
@@ -69,10 +47,6 @@
Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=99063926111686&w=2
Status:
- * Apache->server->register_cleanup
- Report: ?
- Status:
-
* Apache->request(bless {r => $r}, 'My::Apache')
Report:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=98600785703290&w=2
Status:
@@ -81,10 +55,6 @@
Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=94792974200198&w=2
Status:
- * recursion triggered by internal_redirect() called by a pushed handler
- Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=94792974200198&w=2
- Status:
-
* IPC::Open3 issues
Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=98839218229712&w=2
Status:
@@ -93,43 +63,6 @@
Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=97934624332223&w=2
Status:
- * Apache::Status problems?..CGI::Cookie, (dont want no CGI.pm)
- Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=97913833521354&w=2
- Status:
-
- * Gerald's report of Embperl/sub-request/print breakage
- Report: ?
- Status:
-
- * /perl/perl-status?sig dumps core under hpux 10.20
[[EMAIL PROTECTED]]
- Report: ?
- Status:
-
- * $r cannot use many api methods during ChildInit/ChildExit -> SEGV
- Report: ?
- Status:
-
- * bytes_sent are not logged if header don't go through send_http_header(),
- e.g CGI->header(-nph => 1, ...) Eric Cholet <[EMAIL PROTECTED]>
- Report: ?
- Status:
-
- * SIGALRM/flock, Lincoln Stein <[EMAIL PROTECTED]>
- Report: ?
- Status:
-
- * perl_config should not av_shift ARRAY refs from %Apache::ReadConfig::
- Report: ?
- Status:
-
- * die and AUTOLOADed DESTROY == empty $@ (Perl or mod_perl bug?)
- Report: ?
- Status:
-
- * can't multiple Apache::Include->virtual in a single request
- Report: ?
- Status:
-
* files that have been created after the server's (child?) startup are
being reported with negative age with -M test under Apache::Registry.
The workaround is to add $^T = time; at the beginning of the scripts. But
@@ -137,19 +70,6 @@
Report: ?
Status:
- * Apache::Include->virtual should return run() value, not status()
- Report: ?
- Status:
-
- * libapreq: Apache::Cookie format sync w/ CGI.pm
- Report: ?
- Status:
-
- * PERL5LIB foo
- Report: ?
- Status:
-
-
Open Issues or Core Enhancements:
* method handler cached-CVs
@@ -190,9 +110,6 @@
Documentation:
- * remove eg/ directory, it's way out of date and no longer needed now
- with the guide, the books, and piles of Apache::* modules
-
* document Apache::Status Apache::Request preference over CGI.pm
and make it more clear that Apache::Status should not be used in a
production environment, as it adds quite a bit of bloat
@@ -211,3 +128,115 @@
therefor, i don't think this patch should be applied as it
would introduce overhead to support a deprecated feature.
user should simply dereference themselves, print $$foo; -dougm
+
+ * Apache::test
+ Report:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=98278446807561&w=2
+ Status:
+ patch available
+
+ any further development of testing framework should be put
+ into Apache-Test within httpd-test/perl-framework
+ http://httpd.apache.org/test/ -dougm
+
+ * get/set handlers issues
+ Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=95721313917562&w=2
+ Status:
+ patch available
+ http://perl.apache.org/~dougm/set_handlers.pat
+
+ modperl 1.x is in maintainance mode, this change puts the
+ core stablity at risk to support functionality that few
+ require. -dougm
+
+ * $r->args parsing of one=&two=2
+ Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=98018719907031&w=2
+ Status:
+ patch available at
+ http://marc.theaimsgroup.com/?l=apache-modperl&m=98048943129379&w=2
+
+ $r->args and $r->content methods are cheap hacks that
+ probably never should have been written. if they are not
+ good enough as-is, user should use Apache::Request or another
+ library with more robustness.
+
+Known bugs unlikely to be fixed:
+
+ * $r cannot use many api methods during ChildInit/ChildExit -> SEGV
+ Report: ?
+ Status:
+ "don't do that". these hooks were introduced after modperl
+ had already been written around all the hooks which took
+ only a request_rec argument. the "fake" request_rec passed
+ to these new hooks was a quick and dirty hack and will
+ probably stay that way. 2.0 does the right thing.
+
+ * Apache->server->register_cleanup
+ Report: if modperl is linked static, Apache->server->register_cleanup
+ is only called on the first pass during server startup.
+
+ Status:
+ this is a legacy bug related to modperl not doing a complete
+ teardown/startup of the interpreter on every restart, so it
+ only happens the first time a Perl{Require,Module} is loaded.
+ this is done properly with dso however. static users can
+ workaround the bug with PerlFreshRestart or delete $INC{__FILE__}
+
+ * bytes_sent are not logged if header don't go through send_http_header(),
+ e.g CGI->header(-nph => 1, ...) Eric Cholet <[EMAIL PROTECTED]>
+ Report: ?
+
+ Status:
+ does anybody actually use nph script anymore?
+
+ * /perl/perl-status?sig dumps core under hpux 10.20
[[EMAIL PROTECTED]]
+ Report: ?
+
+ Status:
+ can't reproduce, can't fix. perl-status?sig is not very
+ useful info anyhow.
+
+ * perl_config should not av_shift ARRAY refs from %Apache::ReadConfig::
+ Report: ?
+
+ Status:
+ i don't think this is actually a problem for anybody.
+
+ * die and AUTOLOADed DESTROY == empty $@ (Perl or mod_perl bug?)
+ Report: ?
+
+ Status:
+ this report is ages old and haven't heard any reports since.
+ if it is a bug, it is likely in perl. solution in that any
+ case: don't AUTOLOAD DESTROY.
+
+ * can't multiple Apache::Include->virtual in a single request
+ Report: ?
+
+ Status:
+ Apache::Include was indented as an example. the subrequest
+ api is not complicated, just use it directly for this
+ functionality.
+
+ * Apache::Include->virtual should return run() value, not status()
+ Report: ?
+
+ Status: see above.
+
+ * SERVER_MERGE and DIR_MERGE
+ Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=97351976714878&w=2
+ Status:
+ The require() part may be legitimate. personally, I never
+ understood the DIR_CREATE happening before SERVER_CREATE
+ either, but it doesn't seem to affect anything. the double
+ DIR_MERGE is just a misunderstanding on Andy's part and is
+ a result of how Apache handles <Location> before and
+ after translation. --Geoff
+
+ '.' is part of the default @INC, so this shouldn't be a problem.
+
+ as for when the CREATE/MERGE functions are called, that's up
+ to apache when that happens. unless somebody can illustrate
+ that Perl directive handlers are treated any different than
+ C handlers, this is a documentation enhancement, not a bug.
+ the extra DIR_{CREATE,MERGE} is likely related to
+ s->lookup_defaults. -dougm
