Cache:: and IPC::MM
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I know somewhat recently there was a lot of talk about how much faster IPC::MM was for shared memory (Perrin mostly, especially after his OSCON talk). So I went and checked it out, figured out I really liked it, and wanted to use it for my caching mechanism. Now, has anybody already written either a Cache::Cache/Apache::Cache extension to use IPC::MM as the backend, or do I need to just go and do that myself? Searching CPAN I'm not seeing any, but I figured it best to ask the list before I go trying to reinvent a wheel. - -- - --Jayce^ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90fBwA10/0O8cAHgRAiRHAJ9xfZdQ8i4/ENH14qrsOAsjrGTyNwCdHs2k y6E2amYBjcvM3WXjYTTNQGI= =nRHh -END PGP SIGNATURE-
Re: Using Perl END{} with Apache::Registry
Although I can't reproduce the behavior you describe (I get a message in my error log plus the END block runs) I have seen something similar in the past when $@ gets reset by an intervening eval block before Apache::Registry gets a chance to log an error. In my case, I had a DESTROY handler on an object that went out of scope and the DESTROY block had an eval {} block inside of it. The presense of the eval {} block reset $@ to "". The result was the original exception was raised but the value was lost and Apache returned server error w/o a log message. (I solved that specific case by localizing $@ in the DESTROY block.) It doesn't sound like this applies to you since you said you observed the faulty behavior w/ an empty END block, but I thought I'd toss it out there anyway. - Kyle - Original Message - From: "Justin Luster" <[EMAIL PROTECTED]> To: "'Perrin Harkins'" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, November 12, 2002 3:34 PM Subject: RE: Using Perl END{} with Apache::Registry > No. If there is an END block empty or not then the error logging does > not happen. > > By the way do you know of any way to capture what would have been logged > and print it through Apache->something? > > Thanks. > > -Original Message- > From: Perrin Harkins [mailto:perrin@;elem.com] > Sent: Tuesday, November 12, 2002 3:34 PM > To: Justin Luster > Cc: [EMAIL PROTECTED] > Subject: Re: Using Perl END{} with Apache::Registry > > Justin Luster wrote: > > > I have an included file that I'm requiring: > > > > require "test.pl"; > > > > Without the END { } block if the script cannot find test.pl I get a > > Server error 500 and an appropriate error message in the log file. > When > > I include the END{ } block I get no Server Error and no message in the > > log file. It is almost as if the END{ } is overwriting the > > ModPerlRegistry error system. > > > Does it make any difference if you change what's in the END block? > > - Perrin > > > > >
RE: Using Perl END{} with Apache::Registry
No. If there is an END block empty or not then the error logging does not happen. By the way do you know of any way to capture what would have been logged and print it through Apache->something? Thanks. -Original Message- From: Perrin Harkins [mailto:perrin@;elem.com] Sent: Tuesday, November 12, 2002 3:34 PM To: Justin Luster Cc: [EMAIL PROTECTED] Subject: Re: Using Perl END{} with Apache::Registry Justin Luster wrote: > I have an included file that I'm requiring: > > require "test.pl"; > > Without the END { } block if the script cannot find test.pl I get a > Server error 500 and an appropriate error message in the log file. When > I include the END{ } block I get no Server Error and no message in the > log file. It is almost as if the END{ } is overwriting the > ModPerlRegistry error system. Does it make any difference if you change what's in the END block? - Perrin
Re: Using Perl END{} with Apache::Registry
Justin Luster wrote: I have an included file that Im requiring: require test.pl; Without the END { } block if the script cannot find test.pl I get a Server error 500 and an appropriate error message in the log file. When I include the END{ } block I get no Server Error and no message in the log file. It is almost as if the END{ } is overwriting the ModPerlRegistry error system. Does it make any difference if you change what's in the END block? - Perrin
RE: Using Perl END{} with Apache::Registry
Thanks for the reply. Unfortunately I need the END block to run for every request. I just was wondering why it altered the way error messages were logged. Thanks. -Original Message- From: Jim Schueler [mailto:jschueler@;tqis.com] Sent: Tuesday, November 12, 2002 2:41 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Using Perl END{} with Apache::Registry Hello Justin. I've done a little work on a similar problem due to Apache::Registry's unusual treatment of END {} blocks. You may want to take a look at the module I recently submitted: http://www.cpan.org/authors/id/T/TQ/TQISJIM/ChildExit_0-1.tar.gz -Jim > Hi, I'm trying to use the END{ } block in my Perl Scripts to do some > code clean up (making sure files are not locked) at the end of each > request. It seems to be working fine. I'm using Apache::Registry to > run a regular Perl script. I'm having a problem with error messages. > > > > I have an included file that I'm requiring: > > > > require "test.pl"; > > > > Without the END { } block if the script cannot find test.pl I get a > Server error 500 and an appropriate error message in the log file. When > I include the END{ } block I get no Server Error and no message in the > log file. It is almost as if the END{ } is overwriting the > ModPerlRegistry error system. > > > > Any ideas? > > > > Thanks.
RE: Using Perl END{} with Apache::Registry
Hello Justin. I've done a little work on a similar problem due to Apache::Registry's unusual treatment of END {} blocks. You may want to take a look at the module I recently submitted: http://www.cpan.org/authors/id/T/TQ/TQISJIM/ChildExit_0-1.tar.gz -Jim > Hi, I'm trying to use the END{ } block in my Perl Scripts to do some > code clean up (making sure files are not locked) at the end of each > request. It seems to be working fine. I'm using Apache::Registry to > run a regular Perl script. I'm having a problem with error messages. > > > > I have an included file that I'm requiring: > > > > require "test.pl"; > > > > Without the END { } block if the script cannot find test.pl I get a > Server error 500 and an appropriate error message in the log file. When > I include the END{ } block I get no Server Error and no message in the > log file. It is almost as if the END{ } is overwriting the > ModPerlRegistry error system. > > > > Any ideas? > > > > Thanks.
Re: [mp-1 ?] Apache::Util::escape_html could handle single quotation
> some of us on modperl-dev had a discussion with Doug recently about > expanding Apache::Util::escape_html() to do things like HTML::Entities > (such as high-bit characters) and it was decided it was a bad idea. > see: > http://marc.theaimsgroup.com/?l=apache-modperl-cvs&m=101708056429561&w=2 > and doug's reply: > http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=101708105030300&w=2 One additional remark: while suggesting escaping of single quote, I'd vote against escaping national characters in escape HTML. For instance, I generate iso-8859-2 encoded Polish pages and I want my national characters to be left as-is while the text is escaped... To end the whole argumentation: I suggest escaping ' as this character is unsafe in HTML. Simultaneously, I suggest keeping advanced entities out of this utility function.
Re: [mp-1 ?] Apache::Util::escape_html could handle single quotation
> namely "i had a bad feeling about this. we should not be implementing > escape_html to begin with, the functionality should all be in apache." > (...) The main point in this case: someone decided to escape " (double quote) in escape_html. For HTML, ' (single quote) is practically equivalent (and can be used at the same places for the same purpose). I see no reason to differentiate handling of single and double quote while generating HTML pages. The reason to use escape_html vs HTML::Entities is clear - the speed. And at least in my case one needs to escape just <, >, &, " and ' - the characters which can spoil the way browser interprets HTML. -- ( Marcin Kasperski | Software is not released, it is allowed to escape.) ( http://www.mk.w.pl | ) () ( Moje prywatne strony: http://www.kasperski.prv.pl )
syntax and sanity check?
I'm doing a 45 minute seminar at UAB tomorrow on mod_perl, and would be very grateful if anyone would point out holes in this code before I try to show it to a roomful of attendees: #~~ # module for Apache/mod_perl PerlPostReadRequestHandler to redirect # users on the nonsecure port over to SSL (hopefully saving bookmarks) #__ package Apache::PortCorrect; # define the package space use strict; # pragma for clean code use Apache::Constants qw( :response );# installed with mod_perl sub handler {# default methodname my($r) = @_; # the request object return OK if 443 == $r->get_server_port; # ok if already SSL my $uri = "https://myserver.com"; # DNS literal * . (split /\s+/, $r->the_request)[1]; # requested "page" $r->custom_response(MOVED,$uri); # for re-request return MOVED;# page moved! } 1; # guarantee return code for load and PerlPostReadRequestHandler +Apache::PortCorrect If someone is interested in seeing the rest of the presentation, I've posted it at http://thesilentbard.com/ACM%20Seminar.ppt -- if you'd care to post it online anywhere else, please let me know first, but that's cool, too. Any corrections are welcome. I know it isn't clean (I tried to make sure it fit on one slide and didn't get too complicated for the topic, hence such non-portable features as the DNS literal, etc), but suggestions are still very welcome. Thanks all, Paul __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
Re: mp2/httpd2 perlio test fail & register_cleanup CGI.pm error
> t/TEST -v apr/perlio > > and also send the errors from t/logs/error_log. I have resolved this myself. It appears the perlio test failed because of some trivial permission problems in the t/perlio directory. Various files didn't exist or were unwritable by the test script so I touched and chmodded them appropriately. > Also in the future please use t/REPORT script to report problems, as > explained here: > http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems Sorry, I'll do this from now on. > > ModPerl::Registry: Can't locate object method "register_cleanup" via > package > > "Apache::RequestRec" at /usr/local/lib/perl5/5.8.0/CGI.pm line 270. > > this method is defined in Apache::compat. What happens if you add > > PerlModule Apache::compat It works when I use this. Thanks for your reply, Phil.
Using Perl END{} with Apache::Registry
Hi, I’m trying to use the END{ } block in my Perl Scripts to do some code clean up (making sure files are not locked) at the end of each request. It seems to be working fine. I’m using Apache::Registry to run a regular Perl script. I’m having a problem with error messages. I have an included file that I’m requiring: require “test.pl”; Without the END { } block if the script cannot find test.pl I get a Server error 500 and an appropriate error message in the log file. When I include the END{ } block I get no Server Error and no message in the log file. It is almost as if the END{ } is overwriting the ModPerlRegistry error system. Any ideas? Thanks.
Re: Apache::Request + Apache::Filter
Hello, We use this patch (on Apache::Filter 1.019) and it works ok. It won't get you up and running with Apache::Registry, but it will do if you can initialize the filter yourself. Add this to Filter.pm: sub Apache::Request::filter_register { my $r= shift; @ISA = qw(Apache::Request); Apache::filter_register ($r); } Here is the usage in your own code (this is slightly subtle): my $old_r = Apache->request(); my $filtered_r = Apache::Request->instance($old_r)->filter_register(); That should do the trick. There is probably a cleaner way to do it, but this has worked for us. John On Tuesday, November 12, 2002, at 02:22 PM, Richard Clarke wrote: List, Can anyone tell me if a module exists that combines these two modules so that, for example, when using Apache::Dispatch one can create an instance of Apache::Request in the handler without clobbering the overridden methods sent as part of the Apache::Filter object. Before I try and do this I wondered if it had already been done? Apache::RequestFilter would make sense to me but something like this doesn't seem to exist on CPAN. Ric
Re: compiling modperl with mingw on win32
On Tue, 12 Nov 2002, pascal barbedor wrote: > Hi > > on win32, > > I have compiled perl 5.8 with mingw gcc 3.2 and dmake. > it gives a very fast perl. > > is it possible to build mod_perl 1.99_07 with this perl and an > apache 2043 build with msvc6 ? (is it possible to compile > apache with gcc3.2 ?) In looking through some of the list archives of various groups, it looks possible in principle to compile Apache with mingw, but I've no experience doing so. The Apache sources however don't seem to recognize 'mingw' in the configuration set-up. > because I am trying it , and it don't seems to work . > i have > > - probabely harmless no library found for > c:\apache\lib\libapr... at the perl makefile.pl step (though i > can see the files are there) > > and later a lot of undefined references to apr_ in > modperl_handler.c and others. > > is it because there is an incompatibility format between msvc6 > *.lib files and what gcc 3.2 is expecting to find ? >From what I understand, mingw is designed to be compatible at this level, although there's no guarantees ... If you write some simple test program that just calls one of the functions in a library created with msvc6, does it compile and link successfully? The fact that the libraries weren't even found though suggests the build didn't even get to the stage of trying to find the symbols. For one thing, the message above indicates it's looking in an '/Apache/lib' directory - is this where Apache2 lives? If so, might it be a problem with the names of the libraries? The libraries distributed with the Apache Win32 binary don't always have the 'lib' prefix, which may be assumed in the '-l...' link option that mingw uses ... -- best regards, randy kobes
Apache::Request + Apache::Filter
List, Can anyone tell me if a module exists that combines these two modules so that, for example, when using Apache::Dispatch one can create an instance of Apache::Request in the handler without clobbering the overridden methods sent as part of the Apache::Filter object. Before I try and do this I wondered if it had already been done? Apache::RequestFilter would make sense to me but something like this doesn't seem to exist on CPAN. Ric
compiling modperl with mingw on win32
Hi on win32, I have compiled perl 5.8 with mingw gcc 3.2 and dmake. it gives a very fast perl. is it possible to build mod_perl 1.99_07 with this perl and an apache 2043 build with msvc6 ? (is it possible to compile apache with gcc3.2 ?) because I am trying it , and it don't seems to work . i have - probabely harmless no library found for c:\apache\lib\libapr... at the perl makefile.pl step (though i can see the files are there) and later a lot of undefined references to apr_ in modperl_handler.c and others. is it because there is an incompatibility format between msvc6 *.lib files and what gcc 3.2 is expecting to find ? thanks pascal
Re: More Segfaultage - FreeBSD, building apache, ssl, mod_perl from ports
On Tue, Nov 12, 2002 at 04:29:19PM +, Rafiq Ismail (ADMIN) wrote: > I'm a bit irritated by FreeBSD ports at the moment and need somoene to > shine some light. I need to build Apache from ports on a BSD box - it has > to be from ports - but i don't want to include mod_perl in as a dso. > Thus, I'd like to go to ports and 'Make' with a bunch of options which > will compile mod_perl straight into my apache1.3-ssl package. Having run > make on www/apache1.3-ssl and www/mod_perl, all I get is segfaults. I > simply want to run one make to build it in one go. > > How??? > > I'm sure that the BSD users amoungst you have all done it 101 times. > > Help please? Attached is a port i use for OpenBSD. (It needs cleaning, but works for me) There are a bunch of "customizations" but some key points to the Makefile are: DISTFILES= PATCH_LIST_SUP= FAKE_FLAGS= post-patch: Ed. www-mod_perl.tar.gz Description: application/tar-gz
RE: Can't locate object method "new" via package "Apache::Request" (via Mason)...SOLVED
It's hard to generalize because in some cases the shared object file may actually not be installed. However, there should probably be something in the documentation that tells the user to make sure that the LD_LIBRARY_PATH variable and/or the /etc/ld.so.conf file include the usual default installation paths for required packages. -DeAngelo -Original Message- From: Perrin Harkins [mailto:perrin@;elem.com] Sent: Friday, November 08, 2002 1:10 PM To: DeAngelo Lampkin Cc: mod_perl Mailing List Subject: Re: Can't locate object method "new" via package "Apache::Request" (via Mason)...SOLVED DeAngelo Lampkin wrote: > And of course the other reason is that if the solution to the problem > was so obvious from the error message, somebody would have posted a > solution before I figured it out (with help from you guys). There is documentation related to this problem in the troubleshooting section, and if you'd like to generalize it a little so it will be easier for others to find when looking at this type of message, your help would be welcome. The current documentation is here: http://perl.apache.org/docs/1.0/guide/troubleshooting.html#install_driver_Oracle__failed__Can_t_load__DBD_Oracle_Oracle_so__for_module_DBD__Oracle - Perrin
Re: More Segfaultage - FreeBSD, building apache, ssl, mod_perl from ports
On Tue, 12 Nov 2002, Dominic Mitchell wrote: > > I'm sure that the BSD users amoungst you have all done it 101 times. > > Nope, ports only supports mod_perl as a DSO. oh, poop. > The alternative is to use something like apache toolbox[1] to install it > all in one go. If you want to be sneaky, you can always get a list of > files post-install and run it through pkg_create to fake up a package. > It's what the ports makefile does for you behind your back, anyway... Sounds fun. I'll look into pkg_create. Cheers. Rafiq
Re: More Segfaultage - FreeBSD, building apache, ssl, mod_perl from ports
Rafiq Ismail (ADMIN) wrote: I'm a bit irritated by FreeBSD ports at the moment and need somoene to shine some light. I need to build Apache from ports on a BSD box - it has to be from ports - but i don't want to include mod_perl in as a dso. Thus, I'd like to go to ports and 'Make' with a bunch of options which will compile mod_perl straight into my apache1.3-ssl package. Having run make on www/apache1.3-ssl and www/mod_perl, all I get is segfaults. I simply want to run one make to build it in one go. How??? I'm sure that the BSD users amoungst you have all done it 101 times. Nope, ports only supports mod_perl as a DSO. You'd have to mess with www/apache13-ssl/Makefile to do otherwise. It might not be too difficult to do that, however. You'd have to build mod_perl from inside apache rather than the other way around though, I suspect (without doing major contortions, anyway). The alternative is to use something like apache toolbox[1] to install it all in one go. If you want to be sneaky, you can always get a list of files post-install and run it through pkg_create to fake up a package. It's what the ports makefile does for you behind your back, anyway... -Dom [1] http://www.apachetoolbox.com/ -- | Semantico: creators of major online resources | | URL: http://www.semantico.com/ | | Tel: +44 (1273) 72 | | Address: 33 Bond St., Brighton, Sussex, BN1 1RD, UK. |
Re: Apache-Scoreboad parse error when compiling
Ged Haywood wrote: On Tue, 12 Nov 2002, Francesc Guasch wrote: install Apache::VMonitor, but I can't make Apache::Scoreboard-0.10. In file included from DummyScoreboard.xs:14: /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/Apache/include/modules/perl/mod_perl.h:261: parse error before '*' token Well I'd love to see the command which caused these errors, but it looks like either a bug in gcc-3.2-7 or maybe somehow a file is damaged. But both seem very unlikely explanations to me. Thank you for trying, Ged. Have you built mod_perl with gcc-3.2 before? Well, mod_perl works find in this server. I built it myself. This is RH8.0, and it comes with apache2 and mod_perl-1.99 > Was your Perl built with gcc-3.2? I installed the perl binary from RH8.0 If not you probably need to do that first, but I don't think it will help with this particular problem. I'm gonna build it, but I don't think it'll work FWIW I've attached my mod_perl.h (from mod_perl-1.27 sources); as you can see in my file the line which your compiler is complaining about seems to be just another typedef like the others in that part of the I tried with different mod_perl versions, the one that came with RH7.3 and I made the rpm hacking thingie with mod_perl-1.27 from CPAN. I checked the lines that failes and are simple typedefs Did you build your compiler? nope. I'll try perl-5.8 from source first. mod_perl works fine in this RH8.0, I only can't compile Apache::Scoreboard.
Re: AB Segfault on mod_perl Handler
Richard Clarke wrote: List, Does anyone know why apache ab might segfault when accessing one particular mod_perl handler on my site? Is this something I could be doing wrong in my handler (I can't think what.. the page works find in all browsers). Richard, this has nothing to do with mod_perl, other than triggering a bug in ab. Which is not a *mod_perl* problem. You want to post a proper bug report including a core stack backtrace to the httpd-dev list. See: http://httpd.apache.org/lists.html#http-dev __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:stas@;stason.org http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
Re: CGI hangs with Modperl::Registry and apache2.
On Tue, 12 Nov 2002, Roelf Diedericks wrote: > Randy, wouldn't it be a good idea to compile your binary distributions > of mod_perl2 with MP_TRACE enabled, so that we can use > PerlTrace when testing mod_perl2? > > It would just make it easier for compiler lazy people like myself, and > might help us aid the developers in tracking down niggly problems > such as this. That's true, but to get the full debug functionality, one would have to compile perl, apache, and mod_perl with debugging enabled. And not everyone would want that by default, as it comes with speed and size penalties. Also, even with this, it's easier to debug things in this context with Visual Studio present, and if you have this, it'd be better to compile it yourself anyway. Perhaps, if there's enough of a demand, I could make up a package with debugging enabled; that might be worth it at this development stage to help track problems like the ones you've encountered. -- best regards, randy
More Segfaultage - FreeBSD, building apache, ssl, mod_perl fromports
I'm a bit irritated by FreeBSD ports at the moment and need somoene to shine some light. I need to build Apache from ports on a BSD box - it has to be from ports - but i don't want to include mod_perl in as a dso. Thus, I'd like to go to ports and 'Make' with a bunch of options which will compile mod_perl straight into my apache1.3-ssl package. Having run make on www/apache1.3-ssl and www/mod_perl, all I get is segfaults. I simply want to run one make to build it in one go. How??? I'm sure that the BSD users amoungst you have all done it 101 times. Help please? Cheers, Rafiq
AB Segfault on mod_perl Handler
List, Does anyone know why apache ab might segfault when accessing one particular mod_perl handler on my site? Is this something I could be doing wrong in my handler (I can't think what.. the page works find in all browsers). Richard.
Re: Apache-Scoreboad parse error when compiling
Hi there, On Tue, 12 Nov 2002, Francesc Guasch wrote: > I have a RH8.0 with apache-1.3.27 and mod_perl-1.27. I'm trying to > install Apache::VMonitor, but I can't make Apache::Scoreboard-0.10. > In file included from DummyScoreboard.xs:14: > >/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/Apache/include/modules/perl/mod_perl.h:261: > > parse error before '*' token > >/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/Apache/include/modules/perl/mod_perl.h:261: > > warning: data definition has no type or storage class Well I'd love to see the command which caused these errors, but it looks like either a bug in gcc-3.2-7 or maybe somehow a file is damaged. But both seem very unlikely explanations to me. Have you built mod_perl with gcc-3.2 before? Was your Perl built with gcc-3.2? If not you probably need to do that first, but I don't think it will help with this particular problem. FWIW I've attached my mod_perl.h (from mod_perl-1.27 sources); as you can see in my file the line which your compiler is complaining about seems to be just another typedef like the others in that part of the code. I can't see why it should cause a problem. Did you build your compiler? If so did you run the test suites? I'm currently trying to build gcc-3.2 from source and the test suites fail quite miserably. I'm investigating as and when I get a chance. 73, Ged.
Apache-Scoreboad parse error when compiling
I have a RH8.0 with apache-1.3.27 and mod_perl-1.27. I'm trying to install Apache::VMonitor, but I can't make Apache::Scoreboard-0.10. These are the errors I've seen. In file included from DummyScoreboard.xs:14: /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/Apache/include/modules/perl/mod_perl.h:261: parse error before '*' token /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/Apache/include/modules/perl/mod_perl.h:261: warning: data definition has no type or storage class I did use this module long time ago withou problems. And I've searched google and the mailing list archives unsuccessfully. What can be wrong here ? I also have: perl-5.8.0-55 and gcc-3.2-7. -- frankie
Re: use http-equiv to refresh the page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 06 November 2002 15:19, Eric L. Brine wrote: > HTML 4.01 also has a section on META and http-requiv. However, the > only reference to "refresh" is: "Note. Some user agents support the > use of META to refresh the current page after a specified number of > seconds, with the option of replacing it by a different URI. Authors > should __not__ use this technique to forward users to different > pages, as this makes the page inaccessible to some users. Instead, > automatic page forwarding should be done using server-side > redirects." All the HTTP-EQUIV meta tags are relics from static HTML pages. The HTTP server (eg. Apache) reads meta tags from HTML pages and appends all meta tags with HTTP-EQUIV to outgoing HTTP headers. This feature is not available for dynamic content; dynamic pages must set their own headers. > I'm guessing this is because http-equiv is designed to hold an HTTP > header, but there is no such thing as an "Refresh" header in HTTP. There is a Refresh header in HTTP. It's syntax is the same as for the HTTP-EQUIV meta tag. > So http-equiv="refresh" is no longer standard. Of course, this is all > theoretical. In practice, too many people are not easily swayed by a > measily thing such as a standard. UAs are not required to deal with meta tags which contain HTTP-EQUIV content. Both Internet Explorer (at least <6, v6+ may also support them in quirk mode) and Netscape/Mozilla should interpret them if the server does not include them in the real HTTP headers. Some UAs don't do this, eg. Konqueror, and support for them might go away any time without notice, so it should not be used. The CGI module enables the programmer to add arbitrary HTTP headers with the syntax header( -type => 'text/html', -refresh => '0; url=http://www.address.com/' ); See 'perldoc CGI' for more information. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE90OTjnksV4Ys/z5gRAhTxAJ9tv49KSvNt0JRbzf2Uws+wiOIM4ACfdzDX zhojTxLkGITTQT8MkAVACIg= =fQe4 -END PGP SIGNATURE-
Re: CGI hangs with Modperl::Registry and apache2.
Randy, wouldn't it be a good idea to compile your binary distributions of mod_perl2 with MP_TRACE enabled, so that we can use PerlTrace when testing mod_perl2? It would just make it easier for compiler lazy people like myself, and might help us aid the developers in tracking down niggly problems such as this. Pardon the previous direct email. I didn't look before replying :) Regards, Roelf Diedericks.