Scot Martin wrote: [...]
with the IO tracing to see whatexactly happens behind the scenese and what goes wrong. This is
accomplished with:
PerlTrace o
http://perl.apache.org/docs/2.0/user/config/config.html#C_PerlTrace_
Stas, This helped point to the problem, thank you
very much.
Excellent. Good to know that the trace was useful.
After the request was populated into $r, but before doing anything with it, I was, for reasons I can't think of now, sending the xml header, then reading the request, then printing the reply. This all worked fine until I had a large request, then this is what I see with I/O tracing:
mpxs_Apache__RequestRec_print: 39 bytes [<?xml version="1.0" encoding="UTF-8" ?>] mpxs_Apache__RequestRec_print: (flush) 39 bytes [<?xml version="1.0" encoding="UTF-8" ?>] modperl_request_read: wanted 348402b, read 11584b [<t0:Envelope xmlns:t0="http://...]
Once I did the right thing and delayed sending the header until I had a reply to send, all was well.
It seems to me like what I did shouldn't truncate the request, but I realize I had things out of sequence.
Sounds like you had something causing an early flush on STDOUT which causes Apache to send headers right away.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- 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
