Re: Apache::Registry in mod_perl 2

[please don't take the threads off the list] ColinB wrote: --- Stas Bekman <[EMAIL PROTECTED]> wrote: ColinB wrote: So how can I go about installing just Apache::Registry from the mod_perl 1 tar file without having to install ALL of mod_perl 1 ? simply copy it into one of the dirs i

Re: Apache::Registry in mod_perl 2

--- Stas Bekman <[EMAIL PROTECTED]> wrote: > ColinB wrote: > > So how can I go about installing just Apache::Registry from the > > mod_perl 1 tar file without having to install ALL of mod_perl 1 ? > > simply copy it into one of the dirs in your @INC. > >

Re: pnotes and notes not working from Apache::Registry to handler

ticated in > > $r->pnotes so that a perl logging phase handler can stick the user_id in > > the db. I call $r->pnotes('keyname' => 'somevalue'); in an apache > > registry script, and then call $r->pnotes('keyname') in the logging > >

Re: pnotes and notes not working from Apache::Registry to handler

> I'm trying to store data about a user who has authenticated in > $r->pnotes so that a perl logging phase handler can stick the user_id in > the db. I call $r->pnotes('keyname' => 'somevalue'); in an apache > registry script, and then call $r->pn

Re: pnotes and notes not working from Apache::Registry to handler

er who has authenticated in > $r->pnotes so that a perl logging phase handler can stick the user_id in > the db. I call $r->pnotes('keyname' => 'somevalue'); in an apache > registry script, and then call $r->pnotes('keyname') in the logging > ha

pnotes and notes not working from Apache::Registry to handler

Hi, I'm trying to store data about a user who has authenticated in $r->pnotes so that a perl logging phase handler can stick the user_id in the db. I call $r->pnotes('keyname' => 'somevalue'); in an apache registry script, and then call $r->pnotes('keynam

Re: Apache::Registry in mod_perl 2

On Tue, 2003-07-15 at 08:44, ColinB wrote: > So how can I go about installing just Apache::Registry from the > mod_perl 1 tar file without having to install ALL of mod_perl 1 ? Just copy the Apache/Registry.pm file into the same directory that all your other Apache:: modules are in. - Perrin

Re: Apache::Registry in mod_perl 2

ColinB wrote: This page: http://perl.apache.org/docs/2.0/user/porting/compat.html#C_Apache__Registry___C_Apache__PerlRun__and_Friends says that mod_perl 2's ModPerl::Registry does not chdir() into the script's directory, wheras mod_perl 1's Apache::Registry DOES chdir(). It also

Apache::Registry in mod_perl 2

This page: http://perl.apache.org/docs/2.0/user/porting/compat.html#C_Apache__Registry___C_Apache__PerlRun__and_Friends says that mod_perl 2's ModPerl::Registry does not chdir() into the script's directory, wheras mod_perl 1's Apache::Registry DOES chdir(). It also says that this

Re: Apache::Registry -> String Compaction == Less RAM?

[sent it out too early] Stas Bekman wrote: Also see: http://perl.apache.org/docs/2.0/user/handlers/http.html#PerlResponseHandler __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Gu

Re: Apache::Registry -> String Compaction == Less RAM?

Perrin Harkins wrote: On Mon, 2003-07-07 at 11:50, Nigel Hamilton wrote: I thought I could save some RAM by stripping out comments and whitespace before the eval step - so I quickly wrote a Registry-like handler that strips comments. Those don't take up any space in the actual compiled o

Re: Apache::Registry -> String Compaction == Less RAM?

On Mon, 2003-07-07 at 11:50, Nigel Hamilton wrote: > I thought I could save some RAM by stripping out comments and > whitespace before the eval step - so I quickly wrote a Registry-like > handler that strips comments. Those don't take up any space in the actual compiled opcodes. The only sp

Apache::Registry -> String Compaction == Less RAM?

Hi, Apache::Registry slurps in your Perl modules as strings and then evals them. I thought I could save some RAM by stripping out comments and whitespace before the eval step - so I quickly wrote a Registry-like handler that strips comments. Alas, the experiment failed

RE: Apache::Registry incompatible with CGI ?

Perrin Hawkins wrote: >What's the purpose of that loop? I am setting up an array in $DB->{Page}->{'.parameters'}[...] with each entry being the name of a parameter sent by the client. I am then setting up an array for each of these parameters in $DB->{Page}->{}[...] with one value for each sub

Re: Apache::Registry incompatible with CGI ?

Rob Lambden wrote: sub SetupPageArguments() { my ($DB, $nLoop, @Query, $Key, $Value); $DB=shift; @{$DB->{Page}->{'.parameters'}}=$DB->{ApacheReq}->param(); for($nLoop=0; $nLoop<=$#{$DB->{Page}->{'.parameters'}}; $nLoop++) { if(!defined($DB->{ApacheReq}->param($DB->{Page}-

Re: Apache::Registry incompatible with CGI ?

Hi there, On Tue, 4 Feb 2003, Rob Lambden wrote: > I have written a request handler in Perl. I recently changed some code > in this to convert from using CGI within mod_perl to using Apache::Registry. It's generally best to write handlers. If you have written a handler, in general

Apache::Registry incompatible with CGI ?

Hi, I have written a request handler in Perl. I recently changed some code in this to convert from using CGI within mod_perl to using Apache::Registry. The old code was ... $DB->{ApacheReq} = shift; : $DB->{Page} = CGI::new(); : The new code is ... : $DB->{ApacheReq

Re: Sticky pnotes with Apache::Registry

David Kaufman wrote: "John Heitmann" <[EMAIL PROTECTED]> wrote ... in fact, i've avoided using pnotes after seeing similar inconsistencies and reading reports of others having them, too. that was a while back, though. I've used pnotes extensively for exactly this sort of thing and have found it

Re: Sticky pnotes with Apache::Registry

"John Heitmann" <[EMAIL PROTECTED]> wrote ... > Hello, > > I am seeing an issue where it appears that the contents of pnotes does > not get destroyed when code is run inside of Apache::Registry. I first > noticed this when I saw that connections to our db rema

Re: Sticky pnotes with Apache::Registry

John Heitmann <[EMAIL PROTECTED]> writes: [...] > DirectoryIndex index.pl > > DocumentRoot /tmp/web_directory > > > AddHandler perl-script .pl > PerlHandler Apache::Registry > [...] > That httpd.conf combined with the code in the previous mail pl

Re: Sticky pnotes with Apache::Registry

c AddModule mod_dir.c AddModule mod_perl.c DirectoryIndex index.pl DocumentRoot /tmp/web_directory AddHandler perl-script .pl PerlHandler Apache::Registry # Site specific stuff here for completeness but greeked out User me PidFile /tmp/me.httpd.pid Listen 8080 # This just loads Apach

Sticky pnotes with Apache::Registry

Hello, I am seeing an issue where it appears that the contents of pnotes does not get destroyed when code is run inside of Apache::Registry. I first noticed this when I saw that connections to our db remained open after a request was finished (we store the dbi handle in pnotes for inter

Re: Resetting cache Apache::Registry

Justin Luster wrote: I know that when you “require” or “use” helper files in a Perl Script, and you are using Apache::Registry, when changes are made to the helper files they are not recognized until you restart Apache. In the documentation it says that you can change the Apache configuration

RE: Resetting cache Apache::Registry

Thank you. That is a good suggestion. -Original Message- From: Geoffrey Young [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 03, 2002 9:56 AM To: Justin Luster Cc: [EMAIL PROTECTED] Subject: Re: Resetting cache Apache::Registry > The situation is that I?m using a shared ser

Re: Resetting cache Apache::Registry

The situation is that I?m using a shared server from a 3rd party hosting provider and I do not have control over what they have in their Apache configuration file. Every time I make a change to a helper file I need them to restart Apache. on the Cobalt and Ensim systems I have websites at, I

Resetting cache Apache::Registry

I know that when you “require” or “use” helper files in a Perl Script, and you are using Apache::Registry, when changes are made to the helper files they are not recognized until you restart Apache.  In the documentation it says that you can change the Apache configuration file to do this

Re: Executing Apache::Registry cached script from normal mod_perl

Matthew Hodgson wrote: On Fri, 15 Nov 2002, Josh Chamas wrote: Matthew Hodgson wrote: Hi, I have a script which executes under Apache::Registry and resides in /perl/blah.pl. However, it only generates a fragment of a page, and is normally embedded into an html template using SSI with

Re: Executing Apache::Registry cached script from normal mod_perl

On Fri, 15 Nov 2002, Josh Chamas wrote: > Matthew Hodgson wrote: > > Hi, > > > > I have a script which executes under Apache::Registry and resides in > > /perl/blah.pl. However, it only generates a fragment of a page, and is > > normally embedded into an html

Re: Executing Apache::Registry cached script from normal mod_perl

Matthew Hodgson wrote: Hi, I have a script which executes under Apache::Registry and resides in /perl/blah.pl. However, it only generates a fragment of a page, and is normally embedded into an html template using SSI with something like: I am very aware that this would be better implemented

Executing Apache::Registry cached script from normal mod_perl

Hi, I have a script which executes under Apache::Registry and resides in /perl/blah.pl. However, it only generates a fragment of a page, and is normally embedded into an html template using SSI with something like: I am very aware that this would be better implemented as a raw perl module

Re: Using Perl END{} with Apache::Registry

at you are using. There is actually no module called Apache::Registry in mod_perl 2, so I assumed you meant the 1.x series. - Perrin

RE: Using Perl END{} with Apache::Registry

- From: Jim Schueler [mailto:jschueler@;tqis.com] Sent: Tuesday, November 12, 2002 9:02 PM To: Justin Luster Subject: RE: Using Perl END{} with Apache::Registry Pity that the module doesn't help. I spent many hours testing END {} block behavior in Apache::Registry and relied heavily on logged

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

RE: Using Perl END{} with Apache::Registry

day, 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 t

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

RE: Using Perl END{} with Apache::Registry

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.o

RE: Using Perl END{} with Apache::Registry

ing 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. > &

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

Re: Error messages in Apache::Registry

On 17 Sep 2002 at 13:27, Perrin Harkins wrote: > Matt wrote some stuff for the guide explaining why the die handler is not > the best approach. Basically, it means all errors will be treated the > same. Ahh, right. Is this what you're referring to?

Re: Error messages in Apache::Registry

William McKee wrote: >>The way that most people would recommend in A::R or anything else is to >>trap errors with eval blocks and then handle them appropriately. > > I thought I was doing that at a global level by throwing an error with > die() that was caught by CGI::Carp. I'm realizing that it

Re: Error messages in Apache::Registry

ide > > <http://perl.apache.org/docs/1.0/guide/snippets.html#Redirecting_Errors_t > > o_ the_Client_Instead_of_error_log> will not work as given for > > Apache::Registry scripts. > > It should work. The signal handler is called even inside an eval. Hmm, I'll try aga

Error messages in Apache::Registry

Hi folks, I'm a new user to mod_perl. I'm using Apache::Registry to run some scripts that have been written using the CGI::Application framework. Previously, under mod_cgi, I've been using the CGI::Carp set_message method of capturing a die and returning a customized error

Re: Apache::Registry

21 at 14:41, Albert Micheev wrote: > Hallo modperl, > > I think, that there is an error in logic of the Apache::Registry. > > RewriteRule ^/(de|fr|es|ru|tt|en)(/(.*))?$ /cgi-bin/script.pl/$3 [E=LANGUAGE:$1] > > Each call of the script with different languages initiates compilatio

Apache::Registry

Hallo modperl, I think, that there is an error in logic of the Apache::Registry. RewriteRule ^/(de|fr|es|ru|tt|en)(/(.*))?$ /cgi-bin/script.pl/$3 [E=LANGUAGE:$1] Each call of the script with different languages initiates compilation of the script, while in hash $Apache::Registry->{$pack

Re: Apache::Registry and Apache::PerlRun

Boex,Matthew W. wrote: > question, > > can i have both Registry and PerlRun running in the same environment? i > have my cgi scripts running under Apache::Registry in one directory, and > want to run a legacy cgi script under PerlRun in another directory. is this > possi

Re: Apache::Registry and Apache::PerlRun

Boex,Matthew W. wrote: > can i have both Registry and PerlRun running in the same environment? i > have my cgi scripts running under Apache::Registry in one directory, and > want to run a legacy cgi script under PerlRun in another directory. is this > possible? Yes, no pr

Apache::Registry and Apache::PerlRun

question, can i have both Registry and PerlRun running in the same environment? i have my cgi scripts running under Apache::Registry in one directory, and want to run a legacy cgi script under PerlRun in another directory. is this possible? matt

Re: END subroutine in Apache::Registry

tion to understanding the behavior of END blocks in > Apache::Registry scripts, a script writer must realize that any module > invoked via "use" or "include" may work differently than its designer > intended, if that module contains END blocks. great, will add that. T

Re: END subroutine in Apache::Registry

END blocks in Apache::Registry scripts, a script writer must realize that any module invoked via "use" or "include" may work differently than its designer intended, if that module contains END blocks. -Jim On Fri, 12 Jul 2002, Stas Bekman wrote: > Jim Schueler wrote: >

Re: END subroutine in Apache::Registry

. > > > It's pretty clear, and the bit about BEGIN blocks is right next to it, > but it might be worth adding a note about the imbalance between BEGIN > blocks and END blocks under Apache::Registry to cover this issue. I don't think there is really a need, but if we d

Re: END subroutine in Apache::Registry

Hi Jim, Stas, On Fri, 12 Jul 2002, Stas Bekman wrote: > Jim Schueler wrote: > > I just read the fine print: :) Good man. > > Apache::Registry runs BEGIN subroutines just once per child > > process, but END routines run every time a script is run. The > > impli

Re: END subroutine in Apache::Registry

Jim Schueler wrote: > I just read the fine print: Apache::Registry runs BEGIN subroutines just > once per child process, but END routines run every time a script is run. > The implication is that an otherwise robust module may behave unexpectedly > when it's imported by an

END subroutine in Apache::Registry

I just read the fine print: Apache::Registry runs BEGIN subroutines just once per child process, but END routines run every time a script is run. The implication is that an otherwise robust module may behave unexpectedly when it's imported by an Apache::Registry script. Doesn't

Re: Apache::Registry question

Kirk Rogers wrote: > How do i configure the httpd.conf file to maintain two different cgi-bin > directories with Apache::Registry? Not sure if I'm asking the question > correctly so here's a quick explanation. > > I have two cgi-bin directories under one Virtual host

Apache::Registry question

How do i configure the httpd.conf file to maintain two different cgi-bin directories with Apache::Registry? Not sure if I'm asking the question correctly so here's a quick explanation. I have two cgi-bin directories under one Virtual host: Alias /this/cgi-bin/ /usr/local/a

Re: Calling an Apache::ASP page from an Apache::Registry script

Andrew Ho wrote: > I've been investigating other template systems to try to find similar > functionality in an existing package for a non-Tellme related project and > haven't been able to find any embedded-Perl solutions that can be called > from a .pl and still have the benefits of template cachi

Re: Calling an Apache::ASP page from an Apache::Registry script

Hello, AH>...can you call an Apache::ASP page from an Apache::Registry script? AH>Couched in MVC terminology, can I forward control from a .pl controller AH>to a .asp template, and pass arguments in a natural way? JC>The safest thing to do right now would probably be to do an

Re: Calling an Apache::ASP page from an Apache::Registry script

uestion: can you call an Apache::ASP page from an Apache::Registry script? > Couched in MVC terminology, can I forward control from a .pl controller to > a .asp template, and pass arguments in a natural way? > ... The safest thing to do right now would probably be to do an external redi

Calling an Apache::ASP page from an Apache::Registry script

Hello, Apologies if this has been asked before; I searched the archives but couldn't find a reference to this. It's been discussed in the context of MVC design a while back, but I don't have a solid answer to the following question: can you call an Apache::ASP page from an A

Re: scripts running under Apache::Registry and tie()/untie()

P-range > for each user. > > I put it into a directory where every .perl-file runs under > Apache::Registry. > Now I do a tie() once in the .perl-script. Do I have to untie() in the same > script > or is this not necessary because as I understood the perl-script keeps > &quo

scripts running under Apache::Registry and tie()/untie()

very .perl-file runs under Apache::Registry. Now I do a tie() once in the .perl-script. Do I have to untie() in the same script or is this not necessary because as I understood the perl-script keeps "living" as long as the child-process who started it?! Did I get something wrong here?! b

Re: Is 'PerlHandler Apache::Registry MySimplePerlModule' possible?

SessionDataPath /tmp/apache_session > PerlSetVar SessionLockPath /tmp/apache_session_lock > > Alias /modperl /home/czinkos/IMI/apache/modperl > > PerlModule Apache::Registry > SetHandler perl-script > PerlHandler Apache::Registry SetMyCookies > Options ExecC

Is 'PerlHandler Apache::Registry MySimplePerlModule' possible?

/czinkos/IMI/apache/modperl PerlModule Apache::Registry SetHandler perl-script PerlHandler Apache::Registry SetMyCookies Options ExecCGI ... The script is simple. It adds to cookies to the header. e.g. $cookie->bake; I've tried it, but id didn't work

Re: response code under Apache::Registry?

Peter Beardsley wrote: > > This is kind of a bizarre question, but I was wondering if it was > technically possible to set the response code of a script running under > Apache::Registry. The way I usually see it being set is the return value > of the handler routine, but is there

response code under Apache::Registry?

This is kind of a bizarre question, but I was wondering if it was technically possible to set the response code of a script running under Apache::Registry. The way I usually see it being set is the return value of the handler routine, but is there any way to set it? Peter Beardsley

Re: Apache::Registry HEAD fix

g OK... and I can't find any decent online API reference for Apache::RegistryNG. Besides, the edition of "Writing Apache modules with Perl and C" that I'm using doesn't seem to cover all Apache::Registry API. Sigh... > anyway, if you send me a sample script I can play wit

Re: Apache::Registry HEAD fix

Jean-Michel Hiver wrote: > > Hi mod_perl Geeks, > > A few weeks ago I raised the issue of Apache::Registry issuing > incorrect headers in the case of a HEAD request, as it's also > returning the headers. > > Geoffrey Young came up with a subclass of Apache:

Apache::Registry HEAD fix

Hi mod_perl Geeks, A few weeks ago I raised the issue of Apache::Registry issuing incorrect headers in the case of a HEAD request, as it's also returning the headers. Geoffrey Young came up with a subclass of Apache::RegistryNG, and I forgot everything about it until yesterday, w

RE: Apache::Registry HTTP HEAD "feature" fix ;-)

> -Original Message- > From: Jean-Michel Hiver [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 27, 2001 9:02 AM > To: [EMAIL PROTECTED] > Subject: Re: Apache::Registry HTTP HEAD "feature" fix ;-) > > > > this should work for scripts that onl

Re: Apache::Registry HTTP HEAD "feature" fix ;-)

> this should work for scripts that only use print() (without the patch I sent > yesterday :) Looks neat! I'll make sure I'll take a close look at that :-) Cheers, -- == \__ = /\/\ IT'S TIME FOR A DIFFERENT KIND OF WEB / /\__/\ \

RE: Apache::Registry HTTP HEAD "feature" fix ;-)

> -Original Message- > From: Jean-Michel Hiver [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 26, 2001 9:38 AM > To: [EMAIL PROTECTED] > Subject: Re: Apache::Registry HTTP HEAD "feature" fix ;-) > > > > well, I just gave you a patch that work

Re: Apache::Registry HTTP HEAD "feature" fix ;-)

> well, I just gave you a patch that worked :) basically, it only provides a > solution for mod_cgi compatible scripts, but if you're using the mod_perl > API then it is up to you to check $r->header_only and take appropriate > action... True, however your patch also means that it's necessary to

RE: Apache::Registry HTTP HEAD "feature" fix ;-)

> -Original Message- > From: Jean-Michel Hiver [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 26, 2001 9:18 AM > To: [EMAIL PROTECTED] > Subject: Re: Apache::Registry HTTP HEAD "feature" fix ;-) > > > > well, you should be subclassing Apa

Re: Apache::Registry HTTP HEAD "feature" fix ;-)

> well, you should be subclassing Apache::RegistryNG instead of > Apache::Registry - then your method calls would work :) Sorry, Although I'm good at OO-Perl and CGI programming, I'm really quite new to mod_perl thus I really don't know what the fuck I'm doing :-) What

RE: Apache::Registry HTTP HEAD "feature" fix ;-)

> -Original Message- > From: Jean-Michel Hiver [mailto:[EMAIL PROTECTED]] > Sent: Sunday, November 25, 2001 7:43 AM > To: [EMAIL PROTECTED] > Subject: Apache::Registry HTTP HEAD "feature" fix ;-) > > > Hi guys, > > As promised I have been p

Re: Apache::Registry HTTP HEAD "feature" fix ;-)

a fix for Apache::Registry. The > module is called "MKDoc::Registry" because it will be integrated in > the piece of software I'm working on, but feel free to do whatever you > want with it. > > A slight litte issue is that I really don't understand why this

Apache::Registry HTTP HEAD "feature" fix ;-)

Hi guys, As promised I have been producing a fix for Apache::Registry. The module is called "MKDoc::Registry" because it will be integrated in the piece of software I'm working on, but feel free to do whatever you want with it. A slight litte issue is that I really d

Re: Apache::Registry HEAD request also return document body

Adam Prime wrote: >>>The perldoc Apache::Registry says >>>"Apache::Registry - Run unaltered CGI scrips under mod_perl" >>> >>Were your CGI scripts designed to handle HEAD requests? You >>don't have >>to alter them to run under mod_per

RE: Apache::Registry HEAD request also return document body

> > The perldoc Apache::Registry says > > "Apache::Registry - Run unaltered CGI scrips under mod_perl" > > Were your CGI scripts designed to handle HEAD requests? You > don't have > to alter them to run under mod_perl, do you? You didn't have to

Re: Apache::Registry HEAD request also return document body

Jean-Michel Hiver wrote: >>You can subclass Apache::RegistryNG to do what you want and send the >>patch for others to re-use. >> > > The perldoc Apache::Registry says > "Apache::Registry - Run unaltered CGI scrips under mod_perl" Were your CGI scripts

Re: Apache::Registry HEAD request also return document body

Hi All, > Well, you won't save CPU if you need to compute the whole page anyway... > And we're talking of dynamic generated pages, most won't be cached, and those > that will might as well send an Expires: header, in which case the proxy > and browser will cache the data unless the user forces th

Re: Apache::Registry HEAD request also return document body

post: > You can subclass Apache::RegistryNG to do what you want and send the > patch for others to re-use. The perldoc Apache::Registry says "Apache::Registry - Run unaltered CGI scrips under mod_perl" Thus I guess if I have to amend Apache::Registry it might be worth submitti

Re: Apache::Registry HEAD request also return document body

> computing the headers, sure. But there are number of things that you > might want to be in the headers (like date last modified, md5 checksum, > content language, content length, etc) and they need the whole page to > be computed anyway. > > You could argue that sending minimalistic headers to

Re: Apache::Registry HEAD request also return document body

At 03:21 PM 11/23/01 +, Jean-Michel Hiver wrote: >Duh... That's a lot of info for a head request :-) Yes, and that's what I get for using HEAD to test! Yesterday's holliday doesn't help todays thinking. How about patching Apache::Registry? Oh, Stas, of cours

Re: Apache::Registry HEAD request also return document body

> You can subclass Apache::RegistryNG to do what you want and send the > patch for others to re-use. The perldoc Apache::Registry says "Apache::Registry - Run unaltered CGI scrips under mod_perl" Thus I guess if I have to amend Apache::Registry it might be worth submitting a p

Re: Apache::Registry HEAD request also return document body

Jean-Michel Hiver wrote: >>>PROBLEM HERE >>>A head request should * NOT * return the body of the document >>> >>You should check $r->header_only in your handler. >> >>http://thingy.kcilink.com/modperlguide/correct_headers/3_1_HEAD.html >>

Re: Apache::Registry HEAD request also return document body

> Try HEAD on this script. > > #!/usr/local/bin/perl -w > use CGI; > > my $q = CGI->new; > > print $q->header, $q->start_html, > join( "\n", map { "$_ : $ENV{$_}" } keys %ENV), > $q->end_html; I'm still getting the headers. I also have this behavior on other boxes (one on our redha

Re: Apache::Registry HEAD request also return document body

At 02:53 PM 11/23/01 +, Jean-Michel Hiver wrote: > My only concern is that I thought that Apache::Registry was designed > to act as a CGI emulator, allowing not so badly written CGIs to have > mod_perl benefits without having to change them. Right, sorry I completely missed the

Re: Apache::Registry HEAD request also return document body

Hi, Thanks for your quick answer, > >PROBLEM HERE > >A head request should * NOT * return the body of the document > > You should check $r->header_only in your handler. > > http://thingy.kcilink.com/modperlguide/correct_headers/3_1_HEAD.html My only concern is

Re: Apache::Registry HEAD request also return document body

At 11:43 AM 11/23/2001 +, Jean-Michel Hiver wrote: >PROBLEM HERE >A head request should * NOT * return the body of the document You should check $r->header_only in your handler. http://thingy.kcilink.com/modperlguide/correct_headers/3_1_HEAD.html Bill Moseley mailto:[EMAIL PROTECTED]

Apache::Registry HEAD request also return document body

' type CGI scripts on my machine. One is running under Apache::Registry, the other is running as a plain old CGI. Here is what I get: not_mod_perl test (plain CGI, everything works fine) = [root@frogette /]# lynx --dump http://not_mod_perl Hello World! [root@frogette /]# lynx --

Re: Apache::Registry caching of compiled scripts

Nicholas Oxhj <[EMAIL PROTECTED]> said something to this effect on 10/11/2001: > Does anybody know why Apache::Registry caches compiled scripts > by their URI, instead of by their absolute path? Try Apache::RegistryNG, which caches scripts by their filename. (darren) -- Premature

Apache::Registry caching of compiled scripts

Hi Does anybody know why Apache::Registry caches compiled scripts by their URI, instead of by their absolute path? At my site we have quite a lot of virtual hosts, which use the same base of cgi scripts. This causes the same scripts to be compiled and cached several times (one time for each

discussing the future of Apache::Registry and friends

I'm about to start porting Apache::Registry and friends to 2.0, and we are discussing this issue at [EMAIL PROTECTED], so if you aren't on this list yet and want to influence things early, make sure that you subscribe to the list: [EMAIL PROTECTED] and sound your voice if you have

Re: Help Apache::Registry Setup

; directory with that snippet of code, or do all mod-perl files have to live > under the mod-perl folder? The chunk of config that I sent: SetHandler perl-script PerlHandler Apache::Registry Is one of several ways to get mod_perl to run your Perl code instead of something else (like

Re: Help Apache::Registry Setup

From: Purcell, Scott <[EMAIL PROTECTED]> > ...but it IS NOT persistant, or cached. > ...do not see how to make the counter.pl PERSISTANT and to tie the > script to the Apache::Registry? What does your server config look like? Do you have .pl assosiated with cgi-script, or pe

Help Apache::Registry Setup

Hello I am trying to learn how to configure and set up the Apache::Registry to cache a script And I am in the documentaton but still getting lost. I am here http://perl.apache.org/guide/porting.html#Before_you_start_to_code And looking at the Exposting Apache::Registry Secrets I entered the

Re: Throwing die in Apache::Registry

would return a useful error > message rather than just die uninformatively. > > Maybe this is what you were asking about? > > Tom > > At 09:19 AM 5/4/01 +0100, Matt Sergeant wrote: > >On Fri, 4 May 2001, Perrin Harkins wrote: > > > >> on 5/4/01 9:28 AM, Mark Ma

Re: Throwing die in Apache::Registry

[EMAIL PROTECTED] (Matt Sergeant) wrote: >On Fri, 4 May 2001, Perrin Harkins wrote: >> on 5/4/01 9:28 AM, Mark Maunder at [EMAIL PROTECTED] wrote: >> > I have an Apache::Registry script that is using XML::Parser. The >> > parser throws a 'die' cal

Re: Throwing die in Apache::Registry

ED] wrote: >> > I have an Apache::Registry script that is using XML::Parser. The parser throws >> > a >> > 'die' call if it encounters a parse error (Why?). >> >> Because it's an exception and the parser can't continue. >> >>

  1   2   3   4   >