I think the reply in SOAP::Lite or MIME::Entity generate invalid HTTP line endings pointing out that MIME::Entity uses hardcoded \n in various places and has old bugs pertaining to newlines, the simplest approach would be to clone MIME::Entity and replace all \n by \r\n (hardcoded) in its source code.
The less intrusive and far more hacky solution is to post-process the output of MIME::Entity yourself:
open my $output_fh, '>', \my $mime_body or die "In-memory handles are not supported by your version of Per +l."; $mime->print( $output_fh ); close $output_fh; $mime_body =~ s!\n!\r\n!g; # use $mime_body as the string wherever you would use it with SOAP::Pa +ckager # I don't know if the following is valid, using a raw string as a MIME + part: $soap->parts( [$mime_body] );
Maybe you need to mock up a MIME::Entity::NewlineFixed instead which implements just enough of the MIME::Entity interface to make SOAP::Packager happy, but I don't know which parts SOAP::Packager uses.
In reply to Re: Again on SOAP::Lite, MIME::Entity and SOAP::Packager
by Corion
in thread Again on SOAP::Lite, MIME::Entity and SOAP::Packager
by ray.rick.mini
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |