Re: generic question on input filters

2009-04-09 Thread André Warnier
Torsten Foertsch wrote: On Thu 09 Apr 2009, André Warnier wrote: I have the impression that I am getting this Apache error : [Wed Apr 08 22:46:22 2009] [crit] [Wed Apr 08 22:46:22 2009] file http_filters.c, line 1324, assertion "!(((&(bb)->list))->next == (struct apr_bucket *)((char *)((&(bb)->

Re: generic question on input filters

2009-04-09 Thread Torsten Foertsch
On Thu 09 Apr 2009, André Warnier wrote: > I have the impression that I am getting this Apache error : > > [Wed Apr 08 22:46:22 2009] [crit] [Wed Apr 08 22:46:22 2009] file > http_filters.c, line 1324, assertion "!(((&(bb)->list))->next == > (struct apr_bucket *)((char *)((&(bb)->list)) - ((long) (

Re: generic question on input filters

2009-04-09 Thread André Warnier
Torsten Foertsch wrote: On Thu 09 Apr 2009, André Warnier wrote: Suspicion : I cannot read the content, and print nothing when I am called. Instead of accumulating the content and process it all at once at the end, should I process it chunk by chunk ? yes, as I said in my previous mail, do it

Re: generic question on input filters

2009-04-09 Thread Torsten Foertsch
On Thu 09 Apr 2009, André Warnier wrote: > Suspicion : I cannot read the content, and print nothing when I am > called.  Instead of accumulating the content and process it all at > once at the end, should I process it chunk by chunk ? yes, as I said in my previous mail, do it chunkwise. > Is it O

Re: generic question on input filters

2009-04-08 Thread André Warnier
Torsten Foertsch wrote: [...] Thanks for the previous answer and tips. I have written and tried the filter, and now I have a problem (at the end). Anyone knows what that means ? Suspicion : I cannot read the content, and print nothing when I am called. Instead of accumulating the content and

Re: generic question on input filters

2009-04-08 Thread Torsten Foertsch
On Wed 08 Apr 2009, André Warnier wrote: > I want to write a mod_perl input filter, which essentially would > replace some characters from form-posted input on the fly, before > letting the request go to the real application. > The requests are POST, with content encoded in one long string, > URL-e