TED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: internal_redirect and returns
>
>
> [snip]
> > I use this subroutine:
> >
> > sub let_through {
> > my ($self, $r, $p) = @_;
> > $r->set_handlers( PerlAuthzHandler => [\&OK] );
> >
[snip]
I use this subroutine:
sub let_through {
my ($self, $r, $p) = @_;
$r->set_handlers( PerlAuthzHandler => [\&OK] );
$r->set_handlers( PerlAuthenHandler => [\&OK] );
$p && $r->internal_redirect( $p );
return OK;
}
And under some circumstances mig
Rob Bloodgood muttered:
> OK 1: none of the example environments you listed that your programmers are
> in include straight mod_perl... in fact they are all CGI emulation layers of
> varying degrees of protection/dirtiness. Do I read you correctly?
Yes, they're all CGI emulations.
> Well, this
> Rob, thanks for pointing me in the right direction. Your advise
> helped me find a solution that works for my situation.
You're welcome!
> I'm working on an API that sits between an Oracle DB and bunch of web
> application programmers. Unfortunately, the programmers run their
> apps under a
Rob, thanks for pointing me in the right direction. Your advise
helped me find a solution that works for my situation.
I'm working on an API that sits between an Oracle DB and bunch of web
application programmers. Unfortunately, the programmers run their
apps under a variety of perl-handlers (A
> I'm trying to handle an exception using an internal_redirect. I
> can get it to work by redirecting to a static page, but when I try to
> redirect to a modperl handler, I'm run into problems.
>
> Here are the two versions of code (BTW, the handler works fine when I
> access it directly via the
ease ignore the same.
- Original Message -
From: Ken Williams <[EMAIL PROTECTED]>
To: Differentiated Software Solutions Pvt. Ltd <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, September 05, 2000 8:01 PM
Subject: Re: internal_redirect
> [EMAIL PROTECTED] (Differen
[EMAIL PROTECTED] (Differentiated Software Solutions Pvt. Ltd) wrote:
>We corrected R to r. Problem still remains.
>We ran this program as a standalone perl program and even this bombs. Code
>as follows.
>
>#!/usr/bin/perl
>my $r;
>use Apache ();
>
>Apache->request($r);
>
>$r->internal_redirect('h
On Tue, 5 Sep 2000, Matt Sergeant wrote:
> On Tue, 5 Sep 2000, Differentiated Software Solutions Pvt. Ltd wrote:
>
> > Hi,
> >
> > We corrected R to r. Problem still remains.
> > We ran this program as a standalone perl program and even this bombs. Code
> > as follows.
> >
> > #!/usr/bin/perl
On Tue, 5 Sep 2000, Differentiated Software Solutions Pvt. Ltd wrote:
> Hi,
>
> We corrected R to r. Problem still remains.
> We ran this program as a standalone perl program and even this bombs. Code
> as follows.
>
> #!/usr/bin/perl
> my $r;
> use Apache ();
>
> Apache->request($r);
>
> $r-
;[EMAIL PROTECTED]>
Sent: Tuesday, September 05, 2000 12:10 PM
Subject: Re: internal_redirect
>
>
> --On 09/05/00 01:23:04 -0500 Ken Williams <[EMAIL PROTECTED]>
> wrote:
>
> > [EMAIL PROTECTED] (Differentiated Software Solutions Pvt. Ltd) wrote:
> >>
it's Apache>request (lowercase)
- Original Message -
From: Differentiated Software Solutions Pvt. Ltd
To: [EMAIL PROTECTED]
Sent: Monday, September 04, 2000 10:52 PM
Subject: internal_redirect
Hi,
The following code is not working.
use Apache;
Apache->Request->internal_redirect('
--On 09/05/00 01:23:04 -0500 Ken Williams <[EMAIL PROTECTED]>
wrote:
> [EMAIL PROTECTED] (Differentiated Software Solutions Pvt. Ltd) wrote:
>> Hi,
>>
>>The following code is not working.
>>
>> use Apache;
>>
>> Apache->Request->internal_redirect('http://192.168.1.2/smg/html/adce
>> pt_log
[EMAIL PROTECTED] (Differentiated Software Solutions Pvt. Ltd) wrote:
>Hi,
>
>The following code is not working.
>
>use Apache;
>
>Apache->Request->internal_redirect('http://192.168.1.2/smg/html/adcept_logo.gif');
>
>The error is:
>
>Can't locate object method "Request" via package "Apache" at
> Hi All
>
> I have a module that displays a selection of FORMs for the user to pick
> from. The FORMs have TARGET='_BLANK'. The submitted form data is sent to a
> different module which parses the data and uses 'open' to call an external
> perl script to generate a file and returns the full disk
Yes, I agree. But as (I thought) I had mentioned in an early post, it
should be possible to turn on this caching behavior for each individual
request before a call to $r->content or $r->read.
Cheers
Dmitry
On 28 Oct 1999, Greg Stark wrote:
>
> That makes sense for small pieces of data such as
Dmitry Beransky <[EMAIL PROTECTED]> writes:
> My apologies for continuing this topic, but I've been thinking some more
> about this issue over the weekend. I'm still perplexed by this seemingly
> arbitrary limitation on the number of times a request body can be read. It
> seems that, at lea
On Mon, 11 Oct 1999, Dmitry Beransky wrote:
> My apologies for continuing this topic, but I've been thinking some more
> about this issue over the weekend. I'm still perplexed by this seemingly
> arbitrary limitation on the number of times a request body can be read. It
> seems that, at leas
Dmitry Beransky <[EMAIL PROTECTED]> wrote:
>My apologies for continuing this topic, but I've been thinking some more
>about this issue over the weekend. I'm still perplexed by this seemingly
>arbitrary limitation on the number of times a request body can be read. It
>seems that, at least theo
My apologies for continuing this topic, but I've been thinking some more
about this issue over the weekend. I'm still perplexed by this seemingly
arbitrary limitation on the number of times a request body can be read. It
seems that, at least theoretically, it should be possible to cache the
Yes, I'm with Andrei on this. All I want to do is to peek at the content
been passed and redirect the request based on what's in it. I did see
Doug's snippet in the archives, but I decided it didn't apply to me as it
still wasn't offering a way to retain the content.
This limitation of calli
On Friday, October 08, 1999 5:25 PM, Andrei A. Voropaev [SMTP:[EMAIL PROTECTED]]
wrote:
> On Fri, Oct 08, 1999 at 05:05:41PM +0200, Eric Cholet wrote:
> > On Friday, October 08, 1999 3:35 PM, Andrei A. Voropaev
>
> > > Well. I wish you have also mentioned how to unset $r->content()
> > > becaus
On Fri, Oct 08, 1999 at 05:05:41PM +0200, Eric Cholet wrote:
> On Friday, October 08, 1999 3:35 PM, Andrei A. Voropaev
> > Well. I wish you have also mentioned how to unset $r->content()
> > because it reads content only once. Second time returns undef. The
>
> But you shoudn't be radubg $r->co
On Friday, October 08, 1999 3:35 PM, Andrei A. Voropaev
[SMTP:[EMAIL PROTECTED]] wrote:
> On Fri, Oct 08, 1999 at 09:39:30AM +0200, Eric Cholet wrote:
> > On Friday, October 08, 1999 3:35 AM, Dmitry Beransky
[SMTP:[EMAIL PROTECTED]] wrote:
> > > I've been playing around with internal redirects o
On Fri, Oct 08, 1999 at 09:39:30AM +0200, Eric Cholet wrote:
> On Friday, October 08, 1999 3:35 AM, Dmitry Beransky [SMTP:[EMAIL PROTECTED]] wrote:
> > I've been playing around with internal redirects of POST requests. They
> > seem to work fine as long as I don't call Apache::content() or any o
On Friday, October 08, 1999 3:35 AM, Dmitry Beransky [SMTP:[EMAIL PROTECTED]] wrote:
> hi,
>
> I've been playing around with internal redirects of POST requests. They
> seem to work fine as long as I don't call Apache::content() or any other
> function that reads a request's content. However,
Hi Dmitry,
Can you go into some detail how you are currently getting this to work?
I would like to do something like this too. I would even like it if you
could send the redirect back to the user. I have not done an internal
redirect. I was under the impression that a redirect back to the use
27 matches
Mail list logo
