--- Joe Schaefer [EMAIL PROTECTED] wrote:
Beberle [EMAIL PROTECTED] writes:
Right, that's exactly the problem I'm trying to
work
around. Once I've read the POST data, is there
some
way to re-POST it?
Not sure this is addressing your particular problem,
but
let me try to
Beberle [EMAIL PROTECTED] writes:
Ok, I'm getting closer but still not there yet. I've
added a filter like so:
[...]
I've been able to successfully capture the POST data
without removing it from the chain. Problem is, it's
too late. From what I've been able to gather from
printing to
--- Tom Schindl [EMAIL PROTECTED] wrote:
Beberle wrote:
Hi,
I found a similar question posted in the
newsgroups
but no one seemed to have a solution. Here's what
I'm
trying to do. I have a web page that does a POST
to a
remote server. Basiscally, I'm trying to read the
post
Beberle [EMAIL PROTECTED] writes:
Right, that's exactly the problem I'm trying to work
around. Once I've read the POST data, is there some
way to re-POST it?
Not sure this is addressing your particular problem, but
let me try to explain how Apache::Request tries to resolve
this sort of
Hi,
I found a similar question posted in the newsgroups
but no one seemed to have a solution. Here's what I'm
trying to do. I have a web page that does a POST to a
remote server. Basiscally, I'm trying to read the
post data and if it matches a regex, I want to
redirect it. Otherwise, I want
Beberle wrote:
Hi,
I found a similar question posted in the newsgroups
but no one seemed to have a solution. Here's what I'm
trying to do. I have a web page that does a POST to a
remote server. Basiscally, I'm trying to read the
post data and if it matches a regex, I want to
redirect it.
On Mon, Dec 13, 2004 at 01:02:42PM +0100, Tom Schindl wrote:
...
if ($content =~ /some_regex/){
# redirect
} else {
# continue with post
return OK;
}
}
...
The problem with POSTED data is that you can not read them more than
once you can think of it
