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
12 matches
Mail list logo
