rch for "STDIN" on the 1.0 docs (as i use
mod_perl 1.x) did not yeild results that answered my question.
Any help would be greatly appreciated,
kind regards,
simran.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
> You could use
>
> $r->read($buf, $bytes_to_read, [$offset])
>
> if I'm not completely wrong.
>
> See:
> http://perl.apache.org/docs/1.0/api/Apache.html#_r_E_gt_read__buf___bytes_to_readoffset__
It would work if something had not already read the data once from the
filehandle... and since
plugin" and as such is passed things like the request
object, but only after some internal pre-processing.
My ideal situation would be if i could someone query the passed (and
original) $r to give me the raw contents...
>
> Tom
>
> simran wrote:
> >>You could use
Thanks to Tom and Geoff for your helpful hints.
I've got a few ideas which i'm going to try based on your ideas and
hopefully one of them will work.
ps: Geoff, the domain www.modperlcookbook.org seems to have lost its A
record (modperlcookbook.org seems to be fine...).
>
r before... and that
does a "send a status to the browser while still uploading a file"... so
its not too dissimilar to what i wanted to do...
I'm sure the document you have pointed me to will come in very handy
though... thankyou for that :-)
simran.
On Tue, 2004-05-11 at 03:3
than efficient manner..
oh well, it'll suffice until i can get my hands on your solution :-)
> simran wrote:
> >>From initial look though, it looked like it was a generic solution...
> > not ideal, but one that might work...
>
> It seems like a pretty generic pr
wn" sub from a cookbook somewhere, but changed exit
to CORE::exit (as otherwise the process was not really exiting, i know
this is a performance hit, as another apache child will need to start,
but don't know how to get around this).
* I do not have the REAPER subroutine (as per
ove?
Any hints on how to either debug the problem further
or solve the problem (if its a known issue) would
be greatly appreciated.
simran.
===
Server information is: Server: Apache/1.3.27 (Unix)
mod
"separate
logging" from many of the virtual sites... (just logging to a central
spot now)... things seem to be better :-)
simran.
On Wed, 2004-07-21 at 11:46, simran wrote:
> Hi All,
>
> I have recently started having a few issues on our
> mod_perl/apache serv
Any suggestions on how to make the above work, or even how to do the
above (set a cookie and redirect the user) in a much neater way would be
appreciated.
I am using:
* Apache/1.3.27 (Unix) mod_gzip/1.3.19.2a mod_ssl/2.8.14 OpenSSL/0.9.6c DAV/1.0.3
mod_perl/1.28
thanks,
simran.
unning that bit of code, was hoping to use handlers from within
an apache LocationMatch directive, but hey, the TransHandler works :-)
thanks,
simran.
On Wed, 2003-09-24 at 18:30, Frank Maas wrote:
> > Hi All,
> >
> > What i am trying to do is:
> >
> > * If a user
= $request->pnotes("test_key");
warn "TEST VALUE = $value\n";
=
In my apache error log i get:
*** Set document root to /home/testuser/www
*** DocRoot=/home/simran/www
*** TEST VALUE = test_value
(/home/simran/www was the document root before i change
On Fri, 2003-10-17 at 13:07, Geoffrey Young wrote:
> simran wrote:
> > Hi All,
> >
> > I have a PerlTransHandler where i am doing something to the effect of:
> >
> > my $request = instance Apache::Request(shift);
> > $request->document_ro
Hi Frank,
On Fri, 2003-10-17 at 18:21, Frank Maas wrote:
> Simran,
>
> Just trying:
>
> GH> however, any changes made to $r->document_root
> GH> would persist for the entire life of the child, not just the life of
> GH> the current request. for that reason,
ler called for '.($r->is_initial_req() ?
> 'initial' : 'sub').' request for '.$r->uri().'. Document root was
> '.$r->document_root();
>
> and this before you reset document_root...
Tried the above, and i get the following output
thing thereafter, do not see the document
root i had set.
a very confused,
simran.
On Fri, 2003-10-17 at 22:12, Frank Maas wrote:
> >> Can it be that a subrequest (issued (by chance?) to the same child)
> >> is messing things up? You might try adding a warn to the
> >&
On Mon, 2004-12-13 at 22:48 -0700, Tim Pushor wrote:
> >
> My module is an authentication/authorization handler. It worked by
> issuing an access token that gets stored in one of an array of berkeley
> DB's. The browser then either sends the token back to the server in the
> form of a cookie or
17 matches
Mail list logo
