--- 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 explain how Apache::Request tries to
> resolve
> this sort of thing in mp2.
>
> apache 2.x has filters, which can be plugged into
> the I/O
> chain just about anywhere. So if you think of the
> HTTP
> request as a pipeline between the user-agent and
> apache's
> response-handler
>
> [user-agent] -> [intermediate web proxies] ->
> [apache server] ->
>
> [connection filters] -> [protocol filters] ->
> [request filters] ->
>
> ^
> [response-handler]
Ok, I'm getting closer but still not there yet. I've
added a filter like so:
PerlInputFilterHandler Apache::RedirectPost
Its purpose is to grep the POST data for certain key
value pairs and if it matches, set some flag (cookie
or header). Then a handler down the chain can, in
theory, take some action based on this flag.
I also have these declarations:
PerlAccessHandler Apache::GateKeeper
PerlTransHandler Apache::DefaultTrans
PerlHandler Apache::Content
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 the error log, the chain looks like this:
PerlTransHandler --> PerlAccessHandler --> PerlHandler
--> PerlInputFilterHandler
I thought the filter was accessed before the
response-handler. What am I doing wrong?
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
--
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
